| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New trigger option of pg_standby |
| Date: | 2009-05-12 11:27:03 |
| Message-ID: | 1242127623.3843.237.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2009-05-12 at 14:15 +0300, Heikki Linnakangas wrote:
> Here's another idea: Let's modify xlog.c so that when the server asks
> for WAL file X, and restore_command returns "not found", the server
> will not ask for any WAL files >= X again (in that recovery session).
> Presumably if X doesn't exist, no later files will exist either.
That was proposed and rejected earlier, though not in this context.
Sounds fine to me.
I agree that we should simplify/clarify the file request pattern, which
is the source of many difficulties over last few years.
I would further propose that I take pg_standby out as a module, so we
can more easily support earlier releases.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-05-12 11:38:11 | Re: New trigger option of pg_standby |
| Previous Message | Heikki Linnakangas | 2009-05-12 11:15:05 | Re: New trigger option of pg_standby |