Re: [HACKERS] pg_dump not in very good shape

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [HACKERS] pg_dump not in very good shape
Дата
Msg-id Pine.GSO.4.02A.10001171205210.8593-100000@Puma.DoCS.UU.SE
обсуждение исходный текст
Ответ на Re: [HACKERS] pg_dump not in very good shape  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [HACKERS] pg_dump not in very good shape  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Mon, 17 Jan 2000, Tom Lane wrote:

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

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@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Patrick Welche
Дата:
Сообщение: Re: [HACKERS] flex
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] TODO list