From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Joe Carlson <jwcarlson@lbl.gov>
To: pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: custom background worker task for \copy?
Date: Sat, 03 Jun 2023 06:41:22 +0200
Message-ID: <bfd97a7d53a7b6dbeace230648054404666fc23d.camel@cybertec.at> (raw)
In-Reply-To: <8407714E-65BB-40A8-97C8-EC4ACDB43B18@lbl.gov>
References: <8407714E-65BB-40A8-97C8-EC4ACDB43B18@lbl.gov>
On Fri, 2023-06-02 at 11:36 -0700, Joe Carlson wrote:
> I have SQL that does it with \copy (select * from <table> where…) … And that is fine.
> But it would be nice to be able to run the \copy commands in parallel.
> So I was thinking of writing a background worker.
Why don't you go the easy way of using several database connections to run the
parallel COPY statements?
Yours,
Laurenz Albe
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: laurenz.albe@cybertec.at, jwcarlson@lbl.gov
Subject: Re: custom background worker task for \copy?
In-Reply-To: <bfd97a7d53a7b6dbeace230648054404666fc23d.camel@cybertec.at>
References: <8407714E-65BB-40A8-97C8-EC4ACDB43B18@lbl.gov> <bfd97a7d53a7b6dbeace230648054404666fc23d.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox