Fwd: [HACKERS] [streaming replication] 9.1.3 streaming replication bug ?
| От | Michael Nolan |
|---|---|
| Тема | Fwd: [HACKERS] [streaming replication] 9.1.3 streaming replication bug ? |
| Дата | |
| Msg-id | CAOzAqu+3MWmZCMKisuihuNfeqFvJPi7sF53mwaCTKyY_gDZsog@mail.gmail.com обсуждение исходный текст |
| Ответ на | 9.1.3 Standby catchup mode ("hans wulf" <lotu1@gmx.net>) |
| Ответы |
Re: [HACKERS] [streaming replication] 9.1.3 streaming
replication bug ?
|
| Список | pgsql-general |
---------- Forwarded message ---------- From: Michael Nolan <htfoot@gmail.com> Date: Wed, 11 Apr 2012 14:48:18 -0400 Subject: Re: [HACKERS] [GENERAL] [streaming replication] 9.1.3 streaming replication bug ? To: Robert Haas <robertmhaas@gmail.com> On Wed, Apr 11, 2012 at 2:14 PM, Robert Haas <robertmhaas@gmail.com> wrote: > > > We've talked about teaching the master to keep track of how far back > all of its known standbys are, and retaining WAL back to that specific > point, rather than the shotgun approach that is wal_keep_segments. > It's not exactly clear what the interface to that should look like, > though. > > Moreover, how does the database decide when to drop a known standby from the queue because it has failed or the DBA notify the database that a particular standby should no longer be included?
В списке pgsql-general по дате отправления: