Postgres Pro
Downloads
Home   >   mailing lists

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 28144.1201743680@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>)
List pgsql-hackers
Tree view 
Bruce Momjian <bruce@momjian.us> writes:
> Another question --- why don't we just turn off synchronized_seqscans
> when we do COPY TO?  That would fix pg_dump and be transparent.

Enforcing this from the server side seems a pretty bad idea.  Note that
there were squawks about having pg_dump behave this way at all; if the
control is on the pg_dump side then at least we have the chance to make
it a user option later.

Also, you forgot about pg_dump -d.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
Next
From: "Christopher Browne"
Date:
Subject: Re: [PATCHES] Better default_statistics_target