From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: logical changeset generation v5 |
Date: | 2013-09-05 16:56:40 |
Message-ID: | 20130905165640.GA349020@alap2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2013-09-03 11:40:57 -0400, Robert Haas wrote:
> On Fri, Aug 30, 2013 at 11:19 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > 0005 wal_decoding: Log xl_running_xact's at a higher frequency than checkpoints are done
> > * benefits hot standby startup
I tried to update the patch to address the comments you made.
> > 0003 wal_decoding: Allow walsender's to connect to a specific database
> > * biggest problem is how to specify the connection we connect
> > to. Currently with the patch walsender connects to a database if it's
> > not named "replication" (via dbname). Perhaps it's better to invent a
> > replication_dbname parameter?
I've updated the patch so it extends the "replication" startup parameter
to not only specify a boolean but also "database". In the latter case it
will connect to the database specified in "dbname".
As discussed downthread, this patch doesn't have an immediate advantage
for users until the changeset extraction patch itself is
applied. Whether or not it should be applied separately is unclear.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
0002-wal_decoding-Allow-walsender-s-to-connect-to-a-speci.patch | text/x-patch | 11.9 KB |
0003-wal_decoding-Log-xl_running_xact-s-at-a-higher-frequ.patch | text/x-patch | 7.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-09-05 16:57:59 | Re: strange IS NULL behaviour |
Previous Message | Joshua D. Drake | 2013-09-05 16:53:18 | Re: get rid of SQL_ASCII? |