Re: Hot standby and b-tree killed items
От | Gregory Stark |
---|---|
Тема | Re: Hot standby and b-tree killed items |
Дата | |
Msg-id | 877i5wkn3e.fsf@oxford.xeocode.com обсуждение исходный текст |
Ответ на | Re: Hot standby and b-tree killed items (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: Hot standby and b-tree killed items
|
Список | pgsql-hackers |
Simon Riggs <simon@2ndQuadrant.com> writes: > The error message ought to be "snapshot too old", which could raise a > chuckle, so I called it something else. > > The point you raise is a good one and I think we should publish a list > of retryable error messages. I contemplated once proposing a special log > level for a retryable error, but not quite a good idea. I'm a bit concerned about the idea of killing off queries to allow WAL to proceed. While I have nothing against that being an option I think we should be aiming to make it not necessary for correctness and not the default. By default I think WAL replay should stick to stalling WAL replay and only resort to killing queries if the user specifically requests it. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning
В списке pgsql-hackers по дате отправления: