| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: pg_dump scripts are no longer ordinary-user friendly |
| Date: | 2001-03-06 02:07:03 |
| Message-ID: | 3.0.5.32.20010306130703.022f6430@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 20:00 5/03/01 -0500, Tom Lane wrote:
>I suppose this is only a cosmetic issue, but we're going to get
>questions/complaints about it... is there any way to avoid needing
>those UPDATEs?
I definitely prefer it to match the old behaviour, and since by default we
put triggers at the end, we could go back to the old model of only updating
pg_class in a data-only dump/restore.
This only has a problem if the user reorders the restore to put triggers at
the start, and then I suspect they may want them enabled anyway. If anybody
can see another case where this will be a problem, speak up...
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2001-03-06 02:08:14 | Re: pg_restore -U |
| Previous Message | Tom Lane | 2001-03-06 01:55:41 | Re: How to shoot yourself in the foot: kill -9 postmaster |