Tom,
Thank you very much for the enlightenment again!
> > I notice that PostgreSQL does disable triggers but it seems to not
> > disable CHECK constraint:
>
> Why should it?
>
> (Hint: a check constraint that looks at anything but the row being
> checked is broken by definition.)
Maybe my case
"CN" <[EMAIL PROTECTED]> writes:
> I notice that PostgreSQL does disable triggers but it seems to not
> disable CHECK constraint:
Why should it?
(Hint: a check constraint that looks at anything but the row being
checked is broken by definition.)
regards, tom lane
---
Thank you for the reply!
> > Triggers are still fired although option --disable-triggers is applied
> > to pg_restore. The fired triggers abort pg_restore because of the
> > foreign keys violations.
[snip]
> > pg_restore -l db1 >list
> > createdb -E UNICODE db1
> > pg_restore -F c -L list -v -d db
am 06.10.2005, um 22:33:52 +0800 mailte CN folgendes:
> Hi!
>
> 8.0.1 and 8.1 beta.
>
> Triggers are still fired although option --disable-triggers is applied
> to pg_restore. The fired triggers abort pg_restore because of the
> foreign keys violations.
>
> The following restore script used to
Hi!
8.0.1 and 8.1 beta.
Triggers are still fired although option --disable-triggers is applied
to pg_restore. The fired triggers abort pg_restore because of the
foreign keys violations.
The following restore script used to be working but it suddently
doesn't. I don't remember I ever changed this
