Horton

Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Heikki Linnakangas <hlinnaka@iki.fi>, Stephen Frost <sfrost@snowman.net>, Ian Lawrence Barwick <barwick@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-11-30T20:46:19Z
Lists: pgsql-hackers 
Michael Paquier <michael@paquier.xyz> writes:
> So this comes down to 5 items, as per the attached.  Thoughts?

These items look fine to me, except this bit seems a bit awkward:

+     Note that the delayed indexing technique used for <acronym>GIN</acronym>
+     (see <xref linkend="gin-fast-update"/> for details) makes this advice
+     less necessary, but for very large updates it may still be best to
+     drop and recreate the index.

Less necessary than what?  Maybe instead write

      When fastupdate is enabled (see ...), the penalty is much less than
      when it is not.  But for very large updates it may still be best to
      drop and recreate the index.

			regards, tom lane

Commits

  1. doc: Remove more notes about compatibilities with past versions

  2. docs: Remove notes about incompatibilies with very old versions.

  3. doc: Remove reference to pre-8.2 pg_dump behaviour

  4. Remove pg_dump/pg_dumpall support for dumping from pre-8.0 servers.

  5. Revise psql pattern-matching switches as per discussion. The rule is now

  6. Improve description of the pattern matching rules used by psql's \d