From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Logical replication and multimaster |
Date: | 2015-12-11 10:16:08 |
Message-ID: | 20151211101608.GN14789@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015-12-11 18:12:55 +0800, Craig Ringer wrote:
> On 10 December 2015 at 03:19, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > On Sun, Dec 6, 2015 at 10:24 PM, Craig Ringer <craig(at)2ndquadrant(dot)com>
> > wrote:
> > > * A way to securely make a libpq connection from a bgworker without
> > messing
> > > with passwords etc. Generate one-time cookies, sometihng like that.
> >
> > Why would you have the bgworker connect to the database via TCP
> > instead of just doing whatever it wants to do directly?
> pg_dump and pg_restore, mainly, for copying the initial database state.
Well, you don't want to necessarily directly connect from the bgworker,
but from processes started from a bgworker. I guess that's where a good
bit of the Robert's confusion originated.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-12-11 11:48:33 | Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |
Previous Message | Craig Ringer | 2015-12-11 10:12:55 | Re: Logical replication and multimaster |