On Thu, Jan 26, 2012 at 11:48 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Tue, Jan 24, 2012 at 4:39 AM, Thomas Ogrisegg
> <tom-nic@patches.fnord.at> wrote:
>> While testing a backup script, I noticed that pg_basebackup exits with
>> 0, even if it had errors while writing the backup to disk when the
>> backup file is to be sent to stdout. The attached patch should fix this
>> problem (and some special cases when the last write fails).
>
> This part looks like a typo:
>
> + if (fflush (tarfile) != 0)
> + {
> + fprintf(stderr, _("%s:
> error flushing stdout: %s\n"),
> +
> strerror (errno));
> + disconnect_and_exit(1);
> + }
>
> The error is in flushing the tarfile, not stdout, right?
No, in this case tarfile is set to stdout as follows.
-------------
if (strcmp(basedir, "-") == 0)
{
#ifdef HAVE_LIBZ
if (compresslevel != 0)
{
ztarfile = gzdopen(dup(fileno(stdout)), "wb");
if (gzsetparams(ztarfile, compresslevel, Z_DEFAULT_STRATEGY) != Z_OK)
{
fprintf(stderr, _("%s: could not set compression level %d: %s\n"),
progname, compresslevel, get_gz_error(ztarfile));
disconnect_and_exit(1);
}
}
else
#endif
tarfile = stdout;
}
-------------
I don't think that pg_basebackup really needs to fflush() stdout for
each file. Right?
-------------
#endif
if (tarfile != NULL)
- fclose(tarfile);
+ {
+ if (fclose(tarfile) != 0)
+ {
+ fprintf(stderr, _("%s: error closing file \"%s\": %s\n"),
+ progname, filename, strerror (errno));
+ disconnect_and_exit(1);
+ }
+ }
-------------
This message doesn't obey the PostgreSQL message style.
It's guaranteed that the tarfile must not be NULL here, so the above check of
tarfile is not required. The remaining code of pg_basebackup relies on this
assumption.
Attached patch removes the fflush() part, changes the log message and removes
the check of tarfile, as above.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
