On Tue, Jan 18, 2011 at 15:49, Alvaro Herrera
<alvhe...@commandprompt.com> wrote:
> Excerpts from Magnus Hagander's message of mar ene 18 10:47:03 -0300 2011:
>
>> Ok, thanks for clarifying. I've updated to use strerror(). Guess it's
>> time for another patch, PFA :-)
>
> Thanks ... Message nitpick:
> + if (compresslevel > 0)
> + {
> + fprintf(stderr,
> + _("%s: this build does not support compression\n"),
> + progname);
> + exit(1);
> + }
>
> pg_dump uses the following wording:
>
> "WARNING: archive is compressed, but this installation does not support "
> "compression -- no data will be available\n"
>
> So perhaps yours should s/build/installation/
That shows up when a the *archive* is compressed, though? There are a
number of other cases that use build in the backend, such as:
src/backend/utils/misc/guc.c: errmsg("assertion checking
is not
supported by this build")));
src/backend/utils/misc/guc.c: errmsg("Bonjour is not
supported by
this build")));
src/backend/utils/misc/guc.c: errmsg("SSL is not
supported by this
build")));
> Also, in messages of this kind,
> + if (gzsetparams(ztarfile, compresslevel, Z_DEFAULT_STRATEGY)
> != Z_OK)
> + {
> + fprintf(stderr, _("%s: could not set compression level
> %i\n"),
> + progname, compresslevel);
>
> Shouldn't you also be emitting the gzerror()? ... oh I see you're
> already doing it for most gz calls.
It's not clear from the zlib documentation I have that gzerror() works
after a gzsetparams(). Do you have any docs that say differently by
any chance?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
