| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | making write location work (was: Efficient transaction-controlled synchronous replication) |
| Date: | 2011-03-23 15:35:31 |
| Message-ID: | [email protected] |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 18, 2011 at 8:16 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Mar 18, 2011 at 3:52 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>> I agree to get rid of write_location.
>>
>> No, don't remove it.
>>
>> We seem to be just looking for things to tweak without any purpose.
>> Removing this adds nothing for us.
>>
>> We will have the column in the future, it is there now, so leave it.
>
> Well then can we revert the part of your that causes it to not
> actually work any more?
Specifically, if we're not going to remove write location, then I
think we need to apply something like the attached.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| write-location-fix. | application/octet-stream | 567 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radosław Smogura | 2011-03-23 15:50:06 | Re: 2nd Level Buffer Cache |
| Previous Message | Robert Haas | 2011-03-23 15:24:30 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |