Re: pgsql: Minor pg_dump improvements

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Minor pg_dump improvements
Date: 2014-02-09 18:35:46
Message-ID: 20140209183546.GA2921@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> >> I'm pretty sure you broke _CloseArchive with this hunk:
>
> > That'd be pretty frustrating as my testing didn't exhibit any issues.
>
> It's possible that errno is accidentally zero when we get there, but
> the code as-committed surely can't be called bulletproof.

Agreed, oversight on my part.

The only remaining place we still clear errno in pg_dump is in
pg_backup_archive.c:checkSeek() around a similar ftello call, perhaps
that should be changed to check the result instead also?

Thanks,

Stephen

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2014-02-09 18:55:03 Re: pgsql: Minor pg_dump improvements
Previous Message Stephen Frost 2014-02-09 18:31:20 pgsql: Focus on ftello result < 0 instead of errno