Re: [HACKERS] pg_dump not in very good shape

On Mon, 17 Jan 2000, Tom Lane wrote:

> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > On 2000-01-15, Tom Lane mentioned:
> >> I am inclined to go ahead and insert vsnprintf into libpq.
>
> > I think including this in libpq is the wrong way to go. [snip]
> > A better idea would be to do what psql does with snprintf: Just include
> > the [v]snprintf.o file in the compilation (linking) conditionally.
>
> Sorry if I was unclear, but that was exactly what I meant.
>
> BTW, since this is now done in libpq, you could probably remove
> snprintf.o from psql ...

Hmm, maybe this is not what I meant. I meant adding the linking line to
pg_dump, not libpq. But I guess as long as we don't tell anyone about it
(vsnprintf being in libpq) we can safely take it out later if someone has
a better plan.

--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden