| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Marko Kreen <markokr(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [9.1] 2 bugs with extensions |
| Date: | 2012-10-25 16:49:52 |
| Message-ID: | 630.1351183792@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> The fact that SEQUENCE SET is considered pre-data has bitten us several
> times already, eg
> http://archives.postgresql.org/pgsql-bugs/2012-05/msg00084.php
> I think it may be time to bite the bullet and change that (including
> breaking dumpSequence() into two separate functions). I'm a little bit
> worried about the compatibility implications of back-patching such a
> change, though. Is it likely that anybody out there is depending on the
> fact that, eg, pg_dump --section=pre-data currently includes SEQUENCE SET
> items? Personally I think it's more likely that that'd be seen as a
> bug, but ...
Specifically, I'm thinking this, which looks rather bulky but most of
the diff is from reindenting the guts of dumpSequence().
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| treat-sequence-data-as-data.patch | text/x-patch | 16.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-10-25 16:56:16 | Re: ToDo: KNN Search should to support DISTINCT clasuse? |
| Previous Message | Alvaro Herrera | 2012-10-25 16:24:15 | Re: autovacuum truncate exclusive lock round two |