| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Upcoming back-branch releases |
| Date: | 2005-08-16 02:19:56 |
| Message-ID: | 43014D4C.10400@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> My recollection is that that change was way too invasive to be
> reasonable for a back-port. The solutions used for circular reference
> situations (various ALTER commands) probably don't exist very far back
> anyway.
Nah, all you need to do is take the 8.0 pg_dump, hard-code that
--use-set-session-authorization is always enabled, and remove use of
pg_get_serial_sequence IIRC...
>>It could be considered a 'bug' I guess, and could help people upgrading
>>from 7.4...
>
> They could just use the 8.0 pg_dump for that.
Yep. But who knows to do that? :)
My 2c : we have an archive of statically compiled pg_dump binaries on
postgresql.org.
Cheers,
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-08-16 02:33:37 | Re: [PATCHES] enable/disable trigger (Re: Fwd: Open items) |
| Previous Message | Tom Lane | 2005-08-16 02:18:15 | Re: [PATCHES] enable/disable trigger (Re: Fwd: Open items) |