Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
making write location work (was: Efficient transaction-controlled synchronous replication)
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 patch 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: write-location-fix.patch
Description: application/octet-stream (566 bytes)
Description: application/octet-stream (566 bytes)
Responses
- Re: making write location work (was: Efficient transaction-controlled synchronous replication) at 2011-03-23 16:10:12 from Simon Riggs
- Re: making write location work (was: Efficient transaction-controlled synchronous replication) at 2011-03-23 16:44:41 from Tom Lane
pgsql-hackers by date
Next: From: Radosław Smogura Date: 2011-03-23 15:50:06 Subject: Re: 2nd Level Buffer Cache Previous: From: Robert Haas Date: 2011-03-23 15:24:30 Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.