| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump end comment |
| Date: | 2004-03-31 01:36:36 |
| Message-ID: | 406A20A4.6020502@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
>>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.
That assumes you are there at the time of dump...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-31 02:42:11 | Re: logging statement levels |
| Previous Message | Philip Warner | 2004-03-31 01:26:31 | Re: pg_dump end comment |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-31 02:42:11 | Re: logging statement levels |
| Previous Message | Philip Warner | 2004-03-31 01:26:31 | Re: pg_dump end comment |