Re: Bug in copy
| От | Greg Sabino Mullane |
|---|---|
| Тема | Re: Bug in copy |
| Дата | |
| Msg-id | CAKAnmmLOBsFfu4KFrwKLtrVsTKg=YFLmaqSFG-zi70wpKp8GYg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Bug in copy (me nefcanto <sn.1361@gmail.com>) |
| Ответы |
Re: Bug in copy
|
| Список | pgsql-bugs |
On Mon, Feb 24, 2025 at 9:09 AM me nefcanto <sn.1361@gmail.com> wrote:
The point is, the database schema is not in our hands. We don't know what rules exist on each table and what rules change. And it's not practical and feasible to spend resources on keeping our bulk insertion logic with the database changes.
That's a company problem, and not one that can be solved by changing the way COPY works.
Is there a problem in implementing this? After all one expects the most advanced open source database to support this real-world requirement.
We're not going to change Postgres into an ETL application. This thread has given you numerous Postgres-specific solutions, but there is also no shortage of ETL applications you can try out.
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
В списке pgsql-bugs по дате отправления: