On Mon, May 05, 2014 at 08:29:56PM -0400, Bruce Momjian wrote:
On Tue, Apr 22, 2014 at 03:19:15PM -0400, Bruce Momjian wrote:
As is often the case with pg_dump, the problems you saw are a small part
of a larger set of problems in that code --- there is general ignoring of
read and write
On Tue, May 6, 2014 at 09:22:20AM -0400, Noah Misch wrote:
On Mon, May 05, 2014 at 08:29:56PM -0400, Bruce Momjian wrote:
On Tue, Apr 22, 2014 at 03:19:15PM -0400, Bruce Momjian wrote:
As is often the case with pg_dump, the problems you saw are a small part
of a larger set of problems in
On Tue, Apr 22, 2014 at 03:19:15PM -0400, Bruce Momjian wrote:
On Sat, Mar 1, 2014 at 12:27:19PM -0800, Sean Chittenden wrote:
The attached patch fixes the case when `pg_dump -Fd …` is called
on a partition where write(2) fails for some reason or another. In
this case, backup jobs were
On Sat, Mar 1, 2014 at 12:27:19PM -0800, Sean Chittenden wrote:
The attached patch fixes the case when `pg_dump -Fd …` is called
on a partition where write(2) fails for some reason or another. In
this case, backup jobs were returning with a successful exit code even
though most of the files in
The attached patch fixes the case when `pg_dump -Fd …` is called on a partition
where write(2) fails for some reason or another. In this case, backup jobs were
returning with a successful exit code even though most of the files in the dump
directory were all zero length.
I haven’t tested this
