Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour
Date
Msg-id X8XyVaSjh4+7MZBP@paquier.xyz
Whole thread Raw
In response to Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Nov 30, 2020 at 03:46:19PM -0500, Tom Lane wrote:
> 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.

Thanks, that's indeed better.  I used your wording, looked at that
again, and applied that.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: autovac issue with large number of tables
Next
From: Greg Nancarrow
Date:
Subject: Re: Libpq support to connect to standby server as priority