Re: Hot standby, slot ids and stuff
От | Simon Riggs |
---|---|
Тема | Re: Hot standby, slot ids and stuff |
Дата | |
Msg-id | 1231447072.18005.310.camel@ebony.2ndQuadrant обсуждение исходный текст |
Ответ на | Re: Hot standby, slot ids and stuff (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: Hot standby, slot ids and stuff
Re: Hot standby, slot ids and stuff |
Список | pgsql-hackers |
On Thu, 2009-01-08 at 22:31 +0200, Heikki Linnakangas wrote: > Simon Riggs wrote: > > * if FATAL errors occur, yet we have long running transactions then we > > have no way of removing those entries from the recovery procs. Since we > > have a fixed pool of recovery transactions we won't have anywhere to > > store that data. Snapshot sizes are fixed maximum with max_connections, > > so eventually we would not be able to take a snapshot at all, and we'd > > need to have a "ERROR: unable to take valid snapshot". > > When a backend dies with FATAL, it writes an abort record before exiting. > > (I was under the impression it doesn't until few minutes ago myself, > when I actually read the shutdown code :-)) Not in all cases; keep reading :-) The good thing is we have a choice now as to whether we care about that, or not. -- Simon Riggs www.2ndQuadrant.comPostgreSQL Training, Services and Support
В списке pgsql-hackers по дате отправления: