Re: Re: Hot Standby query cancellation and Streaming Replication integration
От | Josh Berkus |
---|---|
Тема | Re: Re: Hot Standby query cancellation and Streaming Replication integration |
Дата | |
Msg-id | 4B8C1DD9.5000903@agliodbs.com обсуждение исходный текст |
Ответ на | Re: Re: Hot Standby query cancellation and Streaming Replication integration (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Re: Hot Standby query cancellation and Streaming Replication
integration
Re: Re: Hot Standby query cancellation and Streaming Replication integration |
Список | pgsql-hackers |
On 3/1/10 11:43 AM, Tom Lane wrote: > Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes: >> Greg Stark wrote: >>> For what it's worth Oracle has an option to have your standby >>> intentionally hold back n minutes behind and I've seen that set to 5 >>> minutes. > >> yeah a lot of people are doing that intentionally... > > It's the old DBA screwup safety valve ... drop the main accounts table, > you have five minutes to stop replication before it's dropped on the > standby. Speaking of which, does the current HS+SR code have a > provision to force the standby to stop tracking WAL and come up live, > even when there's more WAL available? Because that's what you'd need > in order for such a thing to be helpful in that scenario. the "fast" recovery option should do this. You'd need some fast reaction times, though. However, this leaves aside Greg's point about snapshot age and successive queries; does anyone dispute his analysis? Simon? --Josh Berkus
В списке pgsql-hackers по дате отправления: