| From: | "simon(at)2ndquadrant(dot)com" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Lazy Snapshots |
| Date: | 2009-08-21 18:31:31 |
| Message-ID: | 1168239715.9774.1250879491080.JavaMail.open-xchange@oxltgw02.schlund.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19 August 2009 at 00:09 Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> When we discussed Hot Standby at pgCon 2008, we discussed the
> possibility of stopping the replications stream whenever a VACUUM came
> through until any queries currently running on the slave completed. Did
> that approach turn out to be completely unworkable? Why?
It will be an option, in two forms and not the part I was removing. Neither of
those do all the things I want to be able to do, so I had been searching for
another way to do replay and uninterrupted queries.
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | simon@2ndquadrant.com | 2009-08-21 18:41:30 | Re: Lazy Snapshots |
| Previous Message | simon@2ndquadrant.com | 2009-08-21 18:14:47 | Re: XLogFlush |