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
adrian.klaver@aklaver.com
