Re: CLUSTER and synchronized scans and pg_dump et al - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CLUSTER and synchronized scans and pg_dump et al
Date
Msg-id 25999.1201455916@sss.pgh.pa.us
Whole thread Raw
In response to CLUSTER and synchronized scans and pg_dump et al  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: CLUSTER and synchronized scans and pg_dump et al  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Re: CLUSTER and synchronized scans and pg_dump et al  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> Perhaps we should have some form of escape hatch for pg_dump to request real
> physical order when dumping clustered tables.

Yeah, Rae Steining was complaining to me about that off-list a few weeks
ago.  The whole syncscan behavior risks breaking many apps that "always
worked before", even if they were disregarding the letter of the SQL spec.

Maybe a GUC variable to enable/disable syncscan?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Simple row serialization?
Next
From: "Guillaume Smet"
Date:
Subject: Re: CLUSTER and synchronized scans and pg_dump et al