| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | me nefcanto <sn(dot)1361(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Zhang Mingli <zmlpostgres(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Bug in copy |
| Date: | 2025-02-24 15:55:21 |
| Message-ID: | CAKAnmmLOBsFfu4KFrwKLtrVsTKg=YFLmaqSFG-zi70wpKp8GYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Feb 24, 2025 at 9:09 AM me nefcanto <sn(dot)1361(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2025-02-24 15:55:31 | Re: BUG #18822: mailing lists reject mails due to DKIM-signature |
| Previous Message | Greg Sabino Mullane | 2025-02-24 15:47:26 | Re: BUG #18822: mailing lists reject mails due to DKIM-signature |