Tom Lane wrote:
> 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.
OK, but keep in mind if we use synchronized_seqscans in pg_dump we will
have to recognize that GUC forever.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +