Re: Check constraint failure messages

From: Miles Elam <miles(dot)elam(at)productops(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Check constraint failure messages
Date: 2021-04-06 21:18:39
Message-ID: CAALojA9zRXojHtVKg11fh2oUu957gg9LSXMH6pt17LWBvz3bfQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Apr 6, 2021 at 1:59 PM Ron <ronljohnsonjr(at)gmail(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message DAVID Nicolas 2021-04-07 06:41:02 RE: Open source licenses
Previous Message Ron 2021-04-06 20:58:45 Re: Check constraint failure messages