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

From Tom Lane
Subject Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour
Date
Msg-id 1306038.1606769179@sss.pgh.pa.us
Whole thread Raw
In response to Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour  (Michael Paquier <michael@paquier.xyz>)
List 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



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: range_agg
Next
From: Alexander Korotkov
Date:
Subject: Re: Improving spin-lock implementation on ARM.