Re: New trigger option of pg_standby - Mailing list pgsql-hackers

From Tom Lane
Subject Re: New trigger option of pg_standby
Date
Msg-id 1985.1242234105@sss.pgh.pa.us
Whole thread Raw
In response to Re: New trigger option of pg_standby  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: New trigger option of pg_standby  (Simon Riggs <simon@2ndQuadrant.com>)
Re: New trigger option of pg_standby  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: New trigger option of pg_standby  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> I don't think we're going to get this to work reliably without extending 
> the interface between the backend and restore_command. We've discussed 
> many methods and there's always some nasty corner-case like that.

> I think we should leave back-branches as is, and go with Simon's 
> suggestion to add new "recovery_end_command" that's run when the 
> recovery is finished. That's simpler and more reliable than any of the 
> other approaches we've discussed, and might become handy for other 
> purposes as well.

> Does someone want to take a stab at writing a patch for that?

Does this conclusion mean that changing pg_standby is no longer
on the table for 8.4?  It certainly smells more like a new feature
than a bug fix.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_views definition format
Next
From: Simon Riggs
Date:
Subject: Re: New trigger option of pg_standby