public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: me nefcanto <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: David G. Johnston <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: Please implement a catch-all error handler per row, for COPY
Date: Sun, 2 Mar 2025 21:33:07 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAEHBEOBAYsELbjC7KvifHk00jNVJvCRpZkHDML9ebsP48g4w+A@mail.gmail.com>
References: <CAEHBEOCqqkSitU5gx=8aHD3ZeLtRy-1eC=Xs=xB-thFNR9JpYA@mail.gmail.com>
<[email protected]>
<CAKFQuwbRCWP2DMHyW1LABuWAjDFVGE4mPJNfXOeTqzMpeBQ_Hw@mail.gmail.com>
<CAKAnmm+OvPKF5p1vZ1FNs1AidJvBriT_+XBz8UZBpsNy7qiHWQ@mail.gmail.com>
<CAEHBEOBAYsELbjC7KvifHk00jNVJvCRpZkHDML9ebsP48g4w+A@mail.gmail.com>
On 3/2/25 19:44, me nefcanto wrote:
> Thank you all for responding. With respect, I don't understand why COPY
> gets related to ETL. All of the requirements I mentioned above have
> nothing to do with ETL. We have a table of categories. A hierarchical
> table. This is a multitenant app. Hundreds of thousands of records are
> in it. We want to calculate the hierarchical properties (nested set
> models, node depth, determining leaves, materialized paths, etc.) and
> then update the entire table. What does this have to do with ETL? Or as
Pretty sure it defines ETL, extract data from a source, transform it to
meet the properties and load it.
At any rate:
1) ON_ERROR IGNORE only just appeared in Postgres 17.
2) Any further changes to it would constitute a feature change that can
only happen in major version upgrade. The next major version is due this
Fall and development is already well under way. The chances of it making
it in given the time frame is slim, so that pushes a practicable
deadline until Fall of 2026.
3) As I mentioned in a previous post there are packages already out
there that may get you want you want now.
--
Adrian Klaver
[email protected]
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Please implement a catch-all error handler per row, for COPY
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox