1
0
mirror of https://github.com/postgres/postgres.git synced 2025-10-22 14:32:25 +03:00
Files
postgres/doc/src/sgml
Alvaro Herrera b3d24cc0f0 Revert analyze support for partitioned tables
This reverts the following commits:
1b5617eb84 Describe (auto-)analyze behavior for partitioned tables
0e69f705cc Set pg_class.reltuples for partitioned tables
41badeaba8 Document ANALYZE storage parameters for partitioned tables
0827e8af70 autovacuum: handle analyze for partitioned tables

There are efficiency issues in this code when handling databases with
large numbers of partitions, and it doesn't look like there isn't any
trivial way to handle those.  There are some other issues as well.  It's
now too late in the cycle for nontrivial fixes, so we'll have to let
Postgres 14 users continue to manually deal with ANALYZE their
partitioned tables, and hopefully we can fix the issues for Postgres 15.

I kept [most of] be280cdad2 ("Don't reset relhasindex for partitioned
tables on ANALYZE") because while we added it due to 0827e8af70, it is
a good bugfix in its own right, since it affects manual analyze as well
as autovacuum-induced analyze, and there's no reason to revert it.

I retained the addition of relkind 'p' to tables included by
pg_stat_user_tables, because reverting that would require a catversion
bump.
Also, in pg14 only, I keep a struct member that was added to
PgStat_TabStatEntry to avoid breaking compatibility with existing stat
files.

Backpatch to 14.

Discussion: https://postgr.es/m/20210722205458.f2bug3z6qzxzpx2s@alap3.anarazel.de
2021-08-16 17:27:52 -04:00
..
2020-07-05 15:37:57 +02:00
2020-09-10 14:15:26 +02:00
2021-07-16 12:39:23 +02:00
2020-10-26 19:17:05 -04:00
2021-07-01 21:27:39 +02:00
2020-02-26 13:05:30 -08:00
2020-03-29 11:15:11 +02:00
2021-01-29 14:09:41 +13:00
2019-09-08 10:27:29 +02:00
2020-07-18 22:43:35 +09:00
2021-04-07 13:52:26 +02:00
2020-10-19 13:48:00 +02:00
2021-07-16 12:39:23 +02:00
2020-06-07 13:18:36 +02:00
2021-07-05 09:38:17 +05:30
2021-07-29 21:39:40 +02:00
2020-07-18 22:43:35 +09:00
2021-07-16 12:39:23 +02:00
2021-07-05 09:38:17 +05:30
2019-10-25 20:39:41 +02:00
2021-07-16 12:39:23 +02:00
2020-07-18 22:43:35 +09:00
2020-10-19 19:28:54 +03:00
2021-07-16 12:39:23 +02:00
2021-01-02 13:06:25 -05:00
2021-08-13 10:32:16 +02:00
2019-09-08 10:27:29 +02:00
2021-03-15 18:13:42 -03:00
2021-07-16 12:39:23 +02:00
2021-07-16 12:39:23 +02:00
2021-01-05 14:26:37 -05:00
2020-08-28 08:19:12 +02:00
2021-07-16 12:39:23 +02:00
2020-12-23 09:33:20 -05:00
2021-07-05 09:38:17 +05:30
2021-03-18 18:22:18 +01:00
2020-06-07 17:16:30 -04:00
2021-08-06 20:56:18 +02:00
2019-09-08 10:27:29 +02:00
2019-03-27 23:10:23 +01:00
2021-07-16 12:39:23 +02:00
2019-09-08 10:27:29 +02:00

<!-- doc/src/sgml/README.links -->

Linking within DocBook documents can be confusing, so here is a summary:


Intra-document Linking
----------------------

<xref>
	use to get chapter/section number from the title of the target
	link, or xreflabel if defined at the target, or refentrytitle if target
        is a refentry;  has no close tag
	http://www.oasis-open.org/docbook/documentation/reference/html/xref.html

linkend=
	controls the target of the link/xref, required

endterm=
	for <xref>, allows the text of the link/xref to be taken from a
	different link target title

<link>
	use to supply text for the link, only uses linkend, requires </link>
	http://www.oasis-open.org/docbook/documentation/reference/html/link.html
	can be embedded inside of <command>, unlike <xref>


External Linking
----------------

<ulink>
	like <link>, but uses a URL (not a document target);  requires
	</ulink>; if no text is specified, the URL appears as the link
	text
	http://www.oasis-open.org/docbook/documentation/reference/html/ulink.html

url=
	used by <ulink> to specify the URL, required


Guidelines
----------

- For an internal link, if you want to supply text, use <link>, else
  <xref>.

- Specific nouns like GUC variables, SQL commands, and contrib modules
  usually have xreflabels.

- For an external link, use <ulink>, with or without link text.

- xreflabels added to tags prevent the chapter/section for id's from being
  referenced;  only the xreflabel is accessible.  Therefore, use xreflabels
  only when linking is common, and chapter/section information is unneeded.