| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Changing pg_dump default file format |
| Date: | 2013-11-08 03:09:28 |
| Message-ID: | 527C55E8.3020801@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/08/2013 07:33 AM, Joshua D. Drake wrote:
>>
>
> All I want to start is this simple fix. I don't know who is going to
> step up to work on pg_dump/all considering it is the bastard step child
> of the project. We only work on it when we absolutely have to (and CMD
> is just as guilty as the rest).
The change its self is simple; the consequences aren't. We learned that
with bytea_output.
There are two-way compat issues to deal with:
- old pg_dump with new pg_restore
- new pg_dump with old pg_restore
- old pg_dump with new psql
- new pg_dump with old psql
and all of pg_dump, pg_restore, and psql are relevant because of the way
they handle errors and consume pg_dump output.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Harold Giménez | 2013-11-08 03:41:12 | Re: Changing pg_dump default file format |
| Previous Message | Craig Ringer | 2013-11-08 03:07:20 | Re: Changing pg_dump default file format |