| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, 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-04-22 07:43:47 |
| Message-ID: | 1240386261.23905.325.camel@itn_l13_jannike |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2009-04-21 at 09:59 -0700, David Fetter wrote:
> On Tue, Apr 21, 2009 at 12:25:50PM +0100, Simon Riggs wrote:
> > > No, removing trigger file as soon as a non-existant file is
> > > requested still seems simpler than deleting it whenever a timeline
> > > history file is requested.
> >
> > If you do this, then you would have to change the procedure written
> > into the 8.3 docs also. Docs aren't backpatchable.
>
> Are you sure? We've found errors in them before and fixed them.
The proposed change is not a bug fix -- hmmm, or is it?
I think we have a way that does not require this...
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2009-04-22 07:57:23 | Re: Why isn't stats_temp_directory automatically created? |
| Previous Message | Fujii Masao | 2009-04-22 05:09:17 | Re: New trigger option of pg_standby |