Re: [HACKERS] pg_dump not in very good shape - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] pg_dump not in very good shape
Date
Msg-id 20029.948090556@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] pg_dump not in very good shape  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [HACKERS] pg_dump not in very good shape
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.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 ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Temp Table Memory Leak
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] RE: Getting rid of setheapoverride (was Re: [COMMITTERS] heap.c)