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

Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Date: 2011-03-10 21:28:12
Message-ID: AANLkTikmSJNsB=Y6c8t13TE63m_npNY0ktDtOs4ynZv0@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Mon, Mar 7, 2011 at 4:47 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> Anyway, the reload of the configuration file should not
> cause the server to end unexpectedly. IOW, GUC assign hook should
> use GUC_complaint_elevel instead of FATAL, in ereport. The attached
> patch fixes that, and includes two typo fixes.

Committed the typo fixes, and the GUC assign hook fix as a separate commit.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Nicolas BarbierDate: 2011-03-10 21:38:04
Subject: Re: Read uncommitted ever possible?
Previous:From: Bruce MomjianDate: 2011-03-10 21:22:51
Subject: Re: Indent authentication overloading

pgsql-committers by date

Next:From: Tom LaneDate: 2011-03-10 22:31:09
Subject: pgsql: Revert addition of third argument to format_type().
Previous:From: Robert HaasDate: 2011-03-10 21:25:16
Subject: pgsql: Make error handling of synchronous_standby_names consistent.

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