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

Re: Sync Rep Design

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Hannu Krosing <hannu(at)2ndquadrant(dot)com>, greg(at)2ndQuadrant(dot)com, Josh Berkus <josh(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Sync Rep Design
Date: 2011-01-01 22:41:10
Message-ID: 1293921670.1892.65467.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, 2011-01-01 at 21:41 +0200, Heikki Linnakangas wrote:
> On 31.12.2010 23:18, Hannu Krosing wrote:
> > On 31.12.2010 13:40, Heikki Linnakangas wrote:
> >> That thread makes no mention of how to specify which standbys are
> >> synchronous and which are not.
> > The simplest way would be to have separate database users for sync and
> > async standbys ?
> >
> > That would allow any standby with right credentials act as a sync user,
> > and those who are not eligible are not accepted even if they try to act
> > as "a synchronity (?) provider".
> 
> Hmm, access control... We haven't yet discussed what privileges a 
> standby needs to become synchronous. Perhaps it needs to be a separate 
> privilege that can be granted, in addition to the replication privilege?

Perhaps we don't need it, also. Why is that essential in this release?

-- 
 Simon Riggs           http://www.2ndQuadrant.com/books/
 PostgreSQL Development, 24x7 Support, Training and Services
 


In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2011-01-01 23:08:42
Subject: Re: Sync Rep Design
Previous:From: Josh BerkusDate: 2011-01-01 22:40:21
Subject: Re: Sync Rep Design

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