From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Il Mimo di Creta <mimo(dot)creta(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Save failed records into auxiliary table |
Date: | 2020-11-12 15:26:09 |
Message-ID: | CAKFQuwYYZFvhSvSQ0phhcbNyb42uOtLm5aaQq+9eDz-m+7PRjg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Nov 12, 2020 at 2:01 AM Il Mimo di Creta <mimo(dot)creta(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | John Scalia | 2020-11-12 16:18:48 | Working with partition tables |
Previous Message | MichaelDBA | 2020-11-12 15:06:23 | Re: Two postgres masters |