| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Joachim Wieland <joe(at)mcknight(dot)de>, José Arthur Benetasso Villanova <jose(dot)arthur(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: directory archive format for pg_dump |
| Date: | 2010-11-22 17:07:03 |
| Message-ID: | 28890.1290445623@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> But I'm not actually sure we should be preventing mix & match of files
> from different dumps. It might be very useful to do just that sometimes,
> like restoring a recent backup, with the contents of one table replaced
> with older data. A warning would be ok, though.
+1. This mechanism seems like a solution in search of a problem.
Just lose the whole thing, and instead fix pg_dump to complain if
the target directory isn't empty. That should be sufficient to guard
against accidental mixing of different dumps, and as Heikki says
there's not a good reason to prevent intentional mixing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-22 17:08:24 | Re: dblink versus long connection strings |
| Previous Message | Robert Haas | 2010-11-22 17:05:58 | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |