On Thu, Feb 09, 2006 at 04:44:20PM +0200, Marko Kreen wrote: > On 2/7/06, Tom Lane <[EMAIL PROTECTED]> wrote: > > Andrew Rawnsley <[EMAIL PROTECTED]> writes: > > > IMHO the #1 priority in the current PITR/WAL shipping system is to make > > > the > > > standby able to tolerate being shut down and restarted, i.e. actually > > > having > > > a true standby mode and not the current method of doing it only on > > > startup. > > > > How is shutting down the standby a good idea? Seems like that will > > block the master too --- or at least result in WAL log files piling up > > rapidly. If the standby goes off-line, abandoning it and starting from > > a fresh base backup when you are ready to restart it seems like the most > > likely recovery path. For sure I don't see this as the "#1 priority". > > For regular recovery it is indeed unnecessary. But I would also > put this as #1 TODO for long-running hot-standby case. The requirement > to start all over makes current setup rather cumbersome.
What happens right now when you want to bring the standby up? Do you have to kill it out of recovery mode and re-start, forcing it to replay WAL again anyway? > And #2 would be running read-only queries while in recovery :) That would be damn handy :) -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
