| From: | Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(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:02:59 |
| Message-ID: | CAMsr+YFW1MCciTobMvEyaky-nn0WQPLoBndRQujCNCM=vnpn_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
I have the feeling something like this came up on the logical replication
thread. Logical rep needs to efficiently load data via bgworker.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2016-12-12 15:17:53 | Re: Declarative partitioning - another take |
| Previous Message | Craig Ringer | 2016-12-12 15:00:04 | Re: jsonb problematic operators |