From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Fix various possible problems with synchronous replication. |
Date: | 2011-03-18 14:41:51 |
Message-ID: | AANLkTin43NdQMon43tP9mY3jHghHdhnReXywZtTHBDLE@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 18 March 2011 14:23, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Mar 17, 2011 at 1:59 PM, Thom Brown <thom(at)linux(dot)com> wrote:
>> On 17 March 2011 17:55, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> On Thu, Mar 17, 2011 at 1:24 PM, Thom Brown <thom(at)linux(dot)com> wrote:
>>>> errdetail("The transaction has already been committed locally but
>>>> might have not been replicated to the standby.")));
>>>> errdetail("The transaction has committed locally, but may not have
>>>> replicated to the standby.")));
>>>>
>>>> Could we have these saying precisely the same thing?
>>>
>>> Yeah. Which is better?
>>
>> Personally I prefer the 2nd. It reads better somehow.
>
> I hacked on this a bit more and ended up with a hybrid of the two.
> Hope you like it; but anyway it's consistent.
Yes, cheers :)
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-03-18 14:52:13 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
Previous Message | Markus Wanner | 2011-03-18 14:37:26 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
From | Date | Subject | |
---|---|---|---|
Next Message | hom | 2011-03-18 14:44:46 | Re: I am confused after reading codes of PostgreSQL three week |
Previous Message | Markus Wanner | 2011-03-18 14:37:26 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |