Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
Date
Msg-id 415.1201758127@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable  (Bruce Momjian <bruce@momjian.us>)
Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> OK, but keep in mind if we use synchronized_seqscans in pg_dump we will
> have to recognize that GUC forever.

No, because it's being used on the query side, not in the emitted dump.
We have *never* promised that pg_dump version N could dump from server
version N+1 .., in fact, personally I'd like to make that case be a hard
error, rather than something people could override with -i.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Oops - BF:Mastodon just died
Next
From: Decibel!
Date:
Subject: Re: Truncate Triggers