Re: COPY documentation with regard to references constraints

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Dominique Devienne <ddevienne(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: COPY documentation with regard to references constraints
Date: 2024-10-31 12:20:02
Message-ID: 20241031122002.GA4435@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 31, 2024 at 13:15:34 +0100,
Dominique Devienne <ddevienne(at)gmail(dot)com> wrote:
>
>AFAIK, DEFERRABLE is for temporary violations crossing statement boundaries,
>to postpone the enforcement of FKs at COMMIT time of the transaction.
>
>While a single COPY is just one statement, so whether a temporary violation
>for self-referential FKs would occur would be implementation-dependent,
>and thus "neither logical" nor predictable.
>
>Applies to other statement types too.

Thanks. I needed to look more carefully under deferrable where it says
the following:
This controls whether the constraint can be deferred. A constraint that is
not deferrable will be checked immediately after every command.

That is pretty clear.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2024-10-31 13:08:00 Re: COPY documentation with regard to references constraints
Previous Message Dominique Devienne 2024-10-31 12:15:34 Re: COPY documentation with regard to references constraints