| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: synchronous_commit and remote_write |
| Date: | 2012-05-10 22:35:28 |
| Message-ID: | 20120510223528.GD16881@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 09, 2012 at 05:02:57PM -0700, Josh Berkus wrote:
>
> > If so, we should also rename the column "write_location" in pg_stat_replication?
>
> Now that you bring it up, probably. Although not necessarily for 9.2.
>
> > 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.
>
> Yeah, I get what it means. But I'm not the person I'm worried about
> being confused.
So, are we shipping remote_write in beta1?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2012-05-10 22:55:45 | Re: synchronous_commit and remote_write |
| Previous Message | Bruce Momjian | 2012-05-10 22:27:00 | Re: Draft release notes complete |