Re: synchronous_commit and remote_write

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: synchronous_commit and remote_write
Date: 2012-05-09 23:40:01
Message-ID: CAHGQGwGA4J-kqkHP7fj6i8fGXzdJRBFaTdkBQ+fRu6WC=AQWzg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 10, 2012 at 6:23 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> The naming is not arbitrary. -1 to changing it as suggested.
>>
>> It is as Aidan says, a state between receive and fsync, normally
>> referred to as write.
>>
>> Plus the word remote denotes it is on the standby, not the local master.
>>
>> So both words have specific meaning, and IMHO clear meaning.
>
> Clear to a postgres hacker, maybe.  Not at *all* clear to our general users.

If so, we should also rename the column "write_location" in pg_stat_replication?
I named "remote_write (originally write)" after that column. And, in
"remote_write",
internally the master waits for replication until the wait LSN has
reached write_location.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2012-05-09 23:52:04 Re: Can pg_trgm handle non-alphanumeric characters?
Previous Message Euler Taveira 2012-05-09 23:18:54 Re: Can pg_trgm handle non-alphanumeric characters?