| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Configuring synchronous replication |
| Date: | 2010-09-20 21:42:35 |
| Message-ID: | AANLkTinF_hPmjH_1XHGCNLvM7vLQqZHO+A+zWR8kAy=P@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 20 September 2010 22:14, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Well, if you need to talk to "all the other standbys" and see who has
> the furtherst-advanced xlog pointer, it seems like you have to have a
> list somewhere of who they all are.
When they connect to the master to get the stream, don't they in
effect, already talk to the primary with the XLogRecPtr being relayed?
Can the connection IP, port, XLogRecPtr and request time of the
standby be stored from this communication to track the states of each
standby? They would in effect be registering upon WAL stream
request... and no doubt this is a horrifically naive view of how it
works.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-09-20 22:24:35 | Re: Configuring synchronous replication |
| Previous Message | Robert Haas | 2010-09-20 21:14:11 | Re: Configuring synchronous replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-09-20 21:49:55 | Re: Serializable snapshot isolation error logging |
| Previous Message | Robert Haas | 2010-09-20 21:14:11 | Re: Configuring synchronous replication |