Skip site navigation (1) Skip section navigation (2)

Re: 'replication' keyword on .pgpass (Streaming Replication)

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 'replication' keyword on .pgpass (Streaming Replication)
Date: 2010-01-07 08:46:19
Message-ID: 9837222c1001070046x45bfec59qecf65c9974d20c35@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Jan 7, 2010 at 09:26, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:

> The same problem also exists in pg_hba.conf. It's because I introduced
> new keyword "replication" in pg_hba.conf to authenticate the standby
> server. This restriction is not acceptable? If so, I'd need to consider
> an authentication configuration for replication again: introduce new
> configuration file? just change the keyword name to "unpopular" one?...

I certainly think there are a lot of installations out there with a
database named "replication". That doesn't mean it's unacceptable
though.

However, wouldn't it make more logical sense to replace "host/hostssl"
with "replication/replicationssl" rather than overload the database
field?


-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

pgsql-hackers by date

Next:From: Joshua TolleyDate: 2010-01-07 09:09:51
Subject: Hot standby documentation
Previous:From: Magnus HaganderDate: 2010-01-07 08:44:21
Subject: Re: 'replication' keyword on .pgpass (Streaming Replication)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group