Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers.

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Simon Riggs <simon@2ndQuadrant.com>

Cc: Robert Haas <robertmhaas@gmail.com>, Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2012-06-05T21:18:49Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Send new protocol keepalive messages to standby servers.
- 64233902d22b 9.2.0 cited

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