Re: Save failed records into auxiliary table - Mailing list pgsql-admin

From Il Mimo di Creta
Subject Re: Save failed records into auxiliary table
Date
Msg-id CAPDeFrdtJ54Tq2NVr3ywsHiE3bVz=8=B4dHq0jOUPOhNDo9y+w@mail.gmail.com
Whole thread Raw
In response to Re: Save failed records into auxiliary table  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-admin
Thank you David,
I tried other solutions, but at this point I agree this looks like the most viable way to solve the problem.

Thank you for your help


On Thu, Nov 12, 2020 at 4:26 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Thu, Nov 12, 2020 at 2:01 AM Il Mimo di Creta <mimo.creta@gmail.com> wrote:
I would like to save such records, and only such records, in an auxiliary table.

You will probably need to resort to loading the incoming data into an unlogged (and consider temporary) staging table then executing one query to load the known good data into the main table and a second query to load the known bad data into the auxiliary table.  For me this is the most direct solution generally anyway and should be used absent a performance problem necessitating optimization work.

Upsert isn't going to help you load incoming data into an auxiliary table, it can only adjust the data to avoid the conflict relative to the referenced table.

David J.

pgsql-admin by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Working with partition tables
Next
From: John Scalia
Date:
Subject: Re: Working with partition tables