| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, "Hilbert, Sebastian" <Sebastian(dot)Hilbert(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] pg_upgrade ?deficiency |
| Date: | 2013-11-27 00:19:42 |
| Message-ID: | 20131127001942.GA12397@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, Nov 26, 2013 at 03:25:44PM -0800, Kevin Grittner wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> > How are we handling breakage of pg_dump, not pg_dumpall?
>
> That was discussed. Do you have something to add?
I am confused what we are patching. Are we patching pg_dump,
pg_dumpall, or both? Can I see the full patch? Are we propagating
other settings from pg_dump to pg_dumpall, like statement_timeout?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Cura | 2013-11-27 08:20:40 | Re: tracking scripts... |
| Previous Message | Kevin Grittner | 2013-11-26 23:25:44 | Re: [GENERAL] pg_upgrade ?deficiency |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-11-27 01:30:01 | Re: lock on object is already held |
| Previous Message | Tom Lane | 2013-11-27 00:01:38 | Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist |