Re: pg_dump end comment

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump end comment
Date: 2004-03-30 05:33:37
Message-ID: 200403300533.i2U5XbS19589@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)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?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Karel Zak 2004-03-30 07:19:15 Re: [HACKERS] Dates BC.
Previous Message Tom Lane 2004-03-30 05:29:00 Re: pg_dump end comment

Browse pgsql-patches by date

  From Date Subject
Next Message Karel Zak 2004-03-30 07:19:15 Re: [HACKERS] Dates BC.
Previous Message Tom Lane 2004-03-30 05:29:00 Re: pg_dump end comment