Re: [PATCH v12] GSSAPI encryption support

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robbie Harwood <rharwood(at)redhat(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH v12] GSSAPI encryption support
Date: 2016-04-08 18:39:57
Message-ID: CA+Tgmoacxa9iL3jhWBv7JnDUXZNi5DtD8mgavV_LGqQEbPFGBg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 8, 2016 at 2:36 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> While it seems like this particular patch (with myself as committer)
> would meet the requirements stated by the RMT for an extension, having
> considered it over the past day or so, I don't think we should make it a
> policy to allow an extension when it involves a significant rework of
> the patch, as is the case here.

I agree. To be clear, those were intended as necessary but not
necessarily sufficient reasons for extension. I agree that patches
needing significant reworking are not good candidates for extensions.
(But that is my feeling as an RMT member, not an RMT official policy
upon which we have voted.)

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2016-04-08 18:40:01 Re: pgsql: CREATE INDEX ... INCLUDING (column[, ...])
Previous Message Stephen Frost 2016-04-08 18:38:37 Re: pgsql: CREATE INDEX ... INCLUDING (column[, ...])