| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Synchronized scans |
| Date: | 2007-06-08 17:43:51 |
| Message-ID: | 3261.1181324631@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Fri, 2007-06-08 at 11:05 +0100, Heikki Linnakangas wrote:
>> BTW: Should we do the synchronization in the non-page-at-a-time mode?
> http://archives.postgresql.org/pgsql-hackers/2006-09/msg01199.php
> There is a very minor assumption there that scans on pg_class will
> return in the same order. I'm not sure if that's even a problem.
I'm inclined not to worry about that --- the odds of trouble from a
concurrent schema update are at least as large as the odds of trouble
from syncscan-induced variance. The correct fix would be to make ANALYZE
sort the rels by OID, anyhow, not to dumb down the scan.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2007-06-08 18:08:43 | Re: Synchronized scans |
| Previous Message | Jeff Davis | 2007-06-08 17:24:22 | Re: Synchronized scans |