| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers. |
| Date: | 2012-06-05 21:34:56 |
| Message-ID: | CA+U5nMLKUMP+JBJEzmb+HeF6u_mSO9=wqumpjL4EGDtsj8VuEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 5 June 2012 22:18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> 1. Functions - it's fairly easy to add some functions. Initially, we
...
> How badly do we really need these functions right now?
We need a better way of taking these decisions than just black/white
yes/no. It makes the decision more taxing than it needs to be.
Can't we have a trial branch where quarantined patches can be placed
on trial for inclusion in main release?
Plus. if we have extensions, why does adding a function need to force
an initdb?? Why don't we use our own infrastructure?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-05 22:55:34 | Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers. |
| Previous Message | Tom Lane | 2012-06-05 21:18:49 | Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-05 22:55:34 | Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers. |
| Previous Message | Simon Riggs | 2012-06-05 21:21:18 | Re: slow dropping of tables, DropRelFileNodeBuffers, tas |