Horton

Re: pg_dump, pg_dumpall and data durability

Michael Paquier <michael.paquier@gmail.com>

View thread View on postgr.es
From: Michael Paquier <michael.paquier@gmail.com>
To: David Steele <david@pgmasters.net>
Cc: Albe Laurenz <laurenz.albe@wien.gv.at>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2017-03-01T23:32:12Z
Lists: pgsql-hackers 
On Thu, Mar 2, 2017 at 2:26 AM, David Steele <david@pgmasters.net> wrote:
> This patch is in need of a committer.  Any takers?
> I didn't see a lot of enthusiasm from committers on the thread

Stephen at least has showed interest.

> so if nobody picks it up by the end of the CF I'm going to mark the patch RWF.

Yes, that makes sense. If no committer is willing to have a look at
code-level and/or has room for this patch then it is as good as
doomed. Except for bug fixes, I have a couple of other patches that
are piling up so they would likely get the same treatment. There is
nothing really we can do about that.
-- 
Michael

Commits

  1. Sync pg_dump and pg_dumpall output