[PATCH 10/14] Allow walsender's to connect to a specific database - Mailing list pgsql-hackers

From Andres Freund
Subject [PATCH 10/14] Allow walsender's to connect to a specific database
Date
Msg-id 1352942234-3953-10-git-send-email-andres@2ndquadrant.com
Whole thread Raw
In response to logical changeset generation v3  (andres@anarazel.de (Andres Freund))
List pgsql-hackers
Currently the decision whether to connect to a database or not is made by
checking whether the passed "dbname" parameter is "replication". Unfortunately
this makes it impossible to connect a to a database named replication...

This is useful for future walsender commands which need database interaction.
---
 src/backend/postmaster/postmaster.c                |  7 ++++--
 .../libpqwalreceiver/libpqwalreceiver.c            |  4 ++--
 src/backend/replication/walsender.c                | 27 ++++++++++++++++++----
 src/backend/utils/init/postinit.c                  |  5 ++++
 src/bin/pg_basebackup/pg_basebackup.c              |  4 ++--
 src/bin/pg_basebackup/pg_receivexlog.c             |  4 ++--
 src/bin/pg_basebackup/receivelog.c                 |  4 ++--
 7 files changed, 41 insertions(+), 14 deletions(-)


Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: [PATCH 07/14] Introduce InvalidCommandId and declare that to be the new maximum for CommandCounterIncrement
Next
From: Andres Freund
Date:
Subject: [PATCH 09/14] Adjust all *Satisfies routines to take a HeapTuple instead of a HeapTupleHeader