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

pgsql: Avoid assuming there will be only 3 states forsynchronous_commi

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid assuming there will be only 3 states forsynchronous_commi
Date: 2011-04-04 22:24:15
Message-ID: E1Q6sBz-0002Gu-2U@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Avoid assuming there will be only 3 states for synchronous_commit.
Also avoid hardcoding the current default state by giving it the name
"on" and replace with a meaningful name that reflects its behaviour.
Coding only, no change in behaviour.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/88f32b7ca29982f286b61a9d0dd29be4b8a01c25

Modified Files
--------------
src/backend/access/transam/xact.c   |    2 +-
src/backend/postmaster/autovacuum.c |    2 +-
src/backend/utils/misc/guc.c        |    2 +-
src/include/access/xact.h           |    9 ++++++---
src/include/replication/syncrep.h   |    2 +-
5 files changed, 10 insertions(+), 7 deletions(-)

Responses

pgsql-hackers by date

Next:From: Stephen FrostDate: 2011-04-04 22:41:59
Subject: Re: time table for beta1
Previous:From: Aidan Van DykDate: 2011-04-04 22:23:20
Subject: Re: Extensions Dependency Checking

pgsql-committers by date

Next:From: Robert HaasDate: 2011-04-04 23:10:42
Subject: Re: [COMMITTERS] pgsql: Avoid assuming there will be only 3 states for synchronous_commi
Previous:From: Simon RiggsDate: 2011-04-04 21:39:36
Subject: pgsql: Centralise release note items related to recovery andreplicatio

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