At 22:26 5/03/01 -0500, Tom Lane wrote:
>
>> Should we have an option to turn off this feature entirely?
>
>Now that you mention it, is it a feature at all? Or a bug? ISTM poor
>form for a data-only restore to assume it may turn off all pre-existing
>triggers.
Do you recall any of the history - why was it added in the first place? I
vaguely recall something about doing a schema restore then data restore. In
this case, you need to disable triggers, but maybe that should be an option
only. ie. default to no messing with pg_class, but if the user requests it,
output code to disable triggers.
The only thing that worries me in this, is that we are changing the
behaviour from 7.0.
----------------------------------------------------------------
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 |/