| From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CLUSTER and synchronized scans and pg_dump et al |
| Date: | 2008-01-27 19:15:37 |
| Message-ID: | 1d4e0c10801271115g2425c519q9e8ef989c51785ad@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 27, 2008 7:37 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Also, does anyone object to making pg_dump just disable it
> unconditionally? Greg's original gripe only mentioned the case of
> clustered tables, but it'd be kind of a pain to make pg_dump turn it
> on and off again for different tables. And I could see people
> complaining about pg_dump failing to preserve row order even in
> unclustered tables.
+1. I don't think it's worth it to enable it for non clustered tables
and it's always better to keep the order if we can.
--
Guillaume
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gevik Babakhani | 2008-01-27 19:54:21 | MSVC Build error |
| Previous Message | Tom Lane | 2008-01-27 18:37:29 | Re: CLUSTER and synchronized scans and pg_dump et al |