Re: New trigger option of pg_standby

Tom Lane wrote:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
>   
>> That's a lot more drastic change to make in beta. Besides, the proposed 
>> fix required backend changes. I think we should keep it in contrib. (At 
>> least for this release: If we get more integrated replication options in 
>> 8.5, that would be a good time to move pg_standby out of contrib if 
>> that's what we want.)
>>     
>
> The proposed fix requires coordinated changes in the core and
> pg_standby.  That would be a lot *harder* if pg_standby were external.
> Since we've evidently not gotten this API quite right yet, I think we
> should be keeping pg_standby in contrib until we do, ie the API has been
> stable for awhile ...
>
>             
>   
Agreed.

Frankly, if anything it should move from contrib to the core proper. I 
regard it as an essential utility, not an optional extra.

cheers

andrew