agora inbox for [email protected]
help / color / mirror / Atom feedFrom: Joshua D. Drake <[email protected]>
To: Robert Haas <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Rethinking the parameter access hooks for plpgsql's benefit
Date: Mon, 09 Mar 2015 09:53:14 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+TgmoZPNJmP7u_ZB3y33nDqgJrekTfVG6CdtnGvSmfoxHZc-g@mail.gmail.com>
References: <[email protected]>
<CA+TgmoYGAV_RP-sL1MQqA8jYiYefN5YM16wDQS1pLKza0RHG+w@mail.gmail.com>
<[email protected]>
<CA+TgmoZPNJmP7u_ZB3y33nDqgJrekTfVG6CdtnGvSmfoxHZc-g@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-hackers>
On 03/09/2015 09:29 AM, Robert Haas wrote:
>
> On Mon, Mar 9, 2015 at 12:26 PM, Joshua D. Drake <[email protected]> wrote:
>> From the reading the original post it seems like the patch was developed on
>> Sales Force's time, not TGLs. I do not think we get to have an opinion on
>> that.
>
> Salesforce gets to develop their patches whenever they want, but they
> don't get to control the community process for getting those patches
> committed to PostgreSQL.
Did I miss the part of the post that said, (speaking as Tom): FYI, I am
ignoring the commit fest deadline and committing this?
Are we supposed to hold patches when we are post-deadline and not seek
feedback? That seems rather hostile.
>
>> Thank you Tom for the efforts you made here, making the largest used PL
>> better, faster, stronger is exactly the type of micro-changes we need to be
>> looking at for further polish within the database.
>
> So, just to be clear, are you proposing that everybody is exempted
> from the CommitFest deadlines, or just Tom?
I am not suggesting that anyone is exempted from a CommitFest deadline.
I am actually rather hard line that we should be keeping them.
I think it is ridiculous to post on the bad/good/timing of a patch
submission unless there is a case being made that the process isn't
actually being followed. I don't see that here.
In short, soap boxing does nobody any good.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, @cmdpromptinc
Now I get it: your service is designed for a customer
base that grew up with Facebook, watches Japanese seizure
robot anime, and has the attention span of a gnat.
I'm not that user., "Tyler Riddle"
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
view thread (42+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Rethinking the parameter access hooks for plpgsql's benefit
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox