| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andrey Borodin <amborodin(at)acm(dot)org> |
| Subject: | Re: background sessions |
| Date: | 2016-12-12 15:29:27 |
| Message-ID: | CA+TgmoaKL8eFbOrAzo8fn-gn=w1VoEqAJPSEBKaHZURR5jAu0w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 12, 2016 at 10:02 AM, Craig Ringer
<craig(dot)ringer(at)2ndquadrant(dot)com> wrote:
> On 12 Dec. 2016 21:55, "Robert Haas" <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, Dec 11, 2016 at 5:38 AM, Andrew Borodin <borodin(at)octonica(dot)com>
> wrote:
>> 1. As far as I can see, we connot use COPY FROM STDIN in bg session?
>> Since one of purposes is to orchestrate transactions, may be that
>> would be valuable.
>
> A background worker has no client connection, so what would COPY FROM STDIN
> do?
>
> It doesn't make sense. But a bgworker may well want to supply input to COPY.
> A COPY FROM CALLBACK of COPY FROM FILEDESC or whatever.
That's kinda weird, though. I mean, you don't need to go through all
of the COPY code just to call heap_multi_insert() or whatever, do you?
You can hand-roll whatever you need there.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-12-12 15:35:20 | Re: jacana hung after failing to acquire random number |
| Previous Message | Tomas Vondra | 2016-12-12 15:17:53 | Re: Declarative partitioning - another take |