Re: pg_dump end comment

Поиск
Список
Период
Сортировка
От Gavin Sherry
Тема Re: pg_dump end comment
Дата
Msg-id Pine.LNX.4.58.0403301818560.642@linuxworld.com.au
обсуждение исходный текст
Ответ на Re: pg_dump end comment  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: pg_dump end comment  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_dump end comment  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: pg_dump end comment  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Список pgsql-hackers
On Tue, 30 Mar 2004, Bruce Momjian wrote:

> Tom Lane wrote:
> > Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> > > This might seem a bit silly, but is there any chance we could add a
> > > comment at the end of pg_dump text output that says '-- End of dump'?
> >
> > Sure --- while you're at it, put a "beginning of dump" at the start.
> >
> > Is it worth adding the database name and/or other command-line
> > parameters given to pg_dump?
> >
> > One thing to think about is the difference between a bare pg_dump and a
> > pg_dump/pg_restore sequence.  Should these always generate identical
> > text output?  (They do as of CVS tip, I believe, though this was not
> > always true before.)
> >
> > Possibly this is all gilding the lily though...
>
> I like an end-of-dump marker for folks who want to check if the dump got
> truncated somehow.  I can see how to do that for text dumps, but what
> about for tar or custom dumps?

Wouldn't it be more effective to test for non zero return status as this
handles -Fc cases, etc, which would be non-trivial to test.

Gavin


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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: pg_dump end comment
Следующее
От: Andreas Pflug
Дата:
Сообщение: Re: pg_advisor schema proof of concept