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 |/
