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: | Rod Taylor <rbt(at)rbt(dot)ca>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Heading to final release |
Date: | 2003-10-14 00:34:04 |
Message-ID: | 200310140034.h9E0Y4r03856@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Rod Taylor <rbt(at)rbt(dot)ca> writes:
> > I vote to disable the checks for pg_restore if the dumpfile has a check
> > added to ensure it's the same file that was dumped (an MD5 in the
> > header) and it is a full database restore.
> > Individual table restores should require the check.
>
> It is not our business to be making such decisions for the DBA. If
> we're going to provide this at all, it should be in the form of a knob
> the DBA can tweak if *he* thinks it's safe to omit the check.
We could allow the dba to _enable_ the check if they want it, of course.
Basically, default it to checks off rather than on. However, there is
no logic that could distinguish a hand-created dump from one we dumped.
This is another area where a guc variable identifing a dump would help.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-10-14 00:48:13 | Re: [HACKERS] Sun performance - Major discovery! |
Previous Message | Bruce Momjian | 2003-10-14 00:31:56 | Re: fix for strict-alias warnings |