Re: Check constraint failure messages - Mailing list pgsql-general

From Miles Elam
Subject Re: Check constraint failure messages
Date
Msg-id CAALojA9zRXojHtVKg11fh2oUu957gg9LSXMH6pt17LWBvz3bfQ@mail.gmail.com
Whole thread Raw
In response to Re: Check constraint failure messages  (Ron <ronljohnsonjr@gmail.com>)
Responses RE: Check constraint failure messages  (Kevin Brannen <KBrannen@efji.com>)
Re: Check constraint failure messages  (Miles Elam <miles.elam@productops.com>)
List pgsql-general
On Tue, Apr 6, 2021 at 1:59 PM Ron <ronljohnsonjr@gmail.com> wrote:

The blunt force answer is to not use bulk inserts.  Try COPY; it's good at saying which record throws an error.

Sadly, this is a cloud-managed database without direct access to 5432 from outside the VPC and bastian instances are frowned upon by our security folks. Guess I'm stuck with bisecting. Thanks for the confirmation.

pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: Check constraint failure messages
Next
From: DAVID Nicolas
Date:
Subject: RE: Open source licenses