On Tue, Apr 17, 2012 at 3:29 PM, Fujii Masao wrote:
> Okay, patch attached.
Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://
On Tue, Apr 17, 2012 at 9:52 PM, Thom Brown wrote:
> On 16 April 2012 17:21, Fujii Masao wrote:
>> On Sun, Apr 15, 2012 at 12:13 AM, Thom Brown wrote:
>>> No, that's not what I was referring to. If you don't have a standby
>>> (i.e. a single, isolated database cluster with no replication), and
On 16 April 2012 17:21, Fujii Masao wrote:
> On Sun, Apr 15, 2012 at 12:13 AM, Thom Brown wrote:
>> No, that's not what I was referring to. If you don't have a standby
>> (i.e. a single, isolated database cluster with no replication), and
>> its synchronous_commit is set to 'remote_write', what
On Sun, Apr 15, 2012 at 12:13 AM, Thom Brown wrote:
> On 14 April 2012 15:58, Fujii Masao wrote:
>> On Sat, Apr 14, 2012 at 4:16 AM, Thom Brown wrote:
>>> I have a question though. What happens when this is set to "write"
>>> (or "remote_write" as proposed) but it's being used on a standalone
>
On 14 April 2012 15:58, Fujii Masao wrote:
> On Sat, Apr 14, 2012 at 4:16 AM, Thom Brown wrote:
>> I have a question though. What happens when this is set to "write"
>> (or "remote_write" as proposed) but it's being used on a standalone
>> primary? At the moment it's not documented what level o
On Sat, Apr 14, 2012 at 4:16 AM, Thom Brown wrote:
> On 13 April 2012 19:15, Kevin Grittner wrote:
>> Robert Haas wrote:
>>
>>> In my view, remote_write seems a lot more clear than write
>>
>> +1
>>
>> I sure didn't understand it to mean remote_write when I read the
>> subject line.
>
> Whatever
On Sat, Apr 14, 2012 at 10:28 AM, Fujii Masao wrote:
> On Sat, Apr 14, 2012 at 4:57 AM, Guillaume Lelarge
> wrote:
>> On 04/13/2012 08:15 PM, Kevin Grittner wrote:
>>> Robert Haas wrote:
In my view, remote_write seems a lot more clear than write
>>>
>>> +1
>>>
>>> I sure didn't understand i
On Sat, Apr 14, 2012 at 4:57 AM, Guillaume Lelarge
wrote:
> On 04/13/2012 08:15 PM, Kevin Grittner wrote:
>>
>> Robert Haas wrote:
>>
>>> In my view, remote_write seems a lot more clear than write
>>
>>
>> +1
>>
>> I sure didn't understand it to mean remote_write when I read the
>> subject line.
On 04/13/2012 08:15 PM, Kevin Grittner wrote:
Robert Haas wrote:
In my view, remote_write seems a lot more clear than write
+1
I sure didn't understand it to mean remote_write when I read the
subject line.
Neither did I. So definitely +1.
--
Guillaume
http://www.postgresql.fr
http://
On 13 April 2012 19:15, Kevin Grittner wrote:
> Robert Haas wrote:
>
>> In my view, remote_write seems a lot more clear than write
>
> +1
>
> I sure didn't understand it to mean remote_write when I read the
> subject line.
Whatever this option value is named, it needs to be referenced in the
pos
Robert Haas wrote:
> In my view, remote_write seems a lot more clear than write
+1
I sure didn't understand it to mean remote_write when I read the
subject line.
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.
On Thu, Jan 26, 2012 at 1:21 AM, Fujii Masao wrote:
> On Wed, Jan 25, 2012 at 11:12 PM, Simon Riggs wrote:
>> On Wed, Jan 25, 2012 at 1:57 PM, Robert Haas wrote:
>>
>>> I think that this would be a lot more clear if we described this as
>>> synchronous_commit = remote_write rather than just sync
On Wed, Jan 25, 2012 at 11:12 PM, Simon Riggs wrote:
> On Wed, Jan 25, 2012 at 1:57 PM, Robert Haas wrote:
>
>> I think that this would be a lot more clear if we described this as
>> synchronous_commit = remote_write rather than just synchronous_commit
>> = write. Actually, the internal constant
On Wed, Jan 25, 2012 at 1:57 PM, Robert Haas wrote:
> I think that this would be a lot more clear if we described this as
> synchronous_commit = remote_write rather than just synchronous_commit
> = write. Actually, the internal constant is named that way already,
> but it's not exposed as such t
On Wed, Jan 25, 2012 at 1:23 AM, Fujii Masao wrote:
> On Wed, Jan 25, 2012 at 5:35 AM, Jaime Casanova wrote:
>> On Tue, Jan 24, 2012 at 3:22 PM, Simon Riggs wrote:
>>> Add new replication mode synchronous_commit = 'write'.
>>> Replication occurs only to memory on standby, not to disk,
>>> so pro
On Wed, Jan 25, 2012 at 5:35 AM, Jaime Casanova wrote:
> On Tue, Jan 24, 2012 at 3:22 PM, Simon Riggs wrote:
>> Add new replication mode synchronous_commit = 'write'.
>> Replication occurs only to memory on standby, not to disk,
>> so provides additional performance if user wishes to
>> reduce du
16 matches
Mail list logo
