Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers.
Date
Msg-id 24858.1338931129@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers.  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers.  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> 1. Functions - it's fairly easy to add some functions. Initially, we
> can add them as a contrib module, then if an initdb is forced
> elsewhere we can include them in the main server.

While I dislike the idea of a forced initdb at this point, adding a
contrib module that we're going to delete again in the next release
seems considerably worse.  That pushes complexity onto everybody,
not just those beta testers who might wish to upgrade their test
installations to final release.  (And, as we've seen with Andrew's
attempts at back-porting json support, we don't really have that
great of an answer for handling functions migrating into core from
a contrib module.)

How badly do we really need these functions right now?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Unnecessary WAL archiving after failover
Next
From: Simon Riggs
Date:
Subject: Re: slow dropping of tables, DropRelFileNodeBuffers, tas