Date: Thu, 31 Oct 2024 07:20:02 -0500
From: Bruno Wolff III <bruno@wolff.to>
To: Dominique Devienne <ddevienne@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: COPY documentation with regard to references constraints
Message-ID: <20241031122002.GA4435@wolff.to>
Mail-Followup-To: Bruno Wolff III <bruno@wolff.to>,
	Dominique Devienne <ddevienne@gmail.com>,
	pgsql-general@lists.postgresql.org
References: <20241031113832.GA3409@wolff.to>
 <CAFCRh-9dwBkb73x+ckFCn-SDy=n8Fpg3XcGfFAT+MWOm+jp-Tw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <CAFCRh-9dwBkb73x+ckFCn-SDy=n8Fpg3XcGfFAT+MWOm+jp-Tw@mail.gmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://www.postgresql.org/message-id/20241031122002.GA4435%40wolff.to>
Precedence: bulk

On Thu, Oct 31, 2024 at 13:15:34 +0100,
  Dominique Devienne <ddevienne@gmail.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.