Re: [HACKERS] pg_dump not in very good shape

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] pg_dump not in very good shape
Date: 2000-01-17 06:29:16
Message-ID: 20029.948090556@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-01-17 06:38:31 Re: [HACKERS] pg_dump not in very good shape
Previous Message Bruce Momjian 2000-01-17 06:19:19 Re: [HACKERS] pg_dump not in very good shape