Re: Procedure for feature requests?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tim Landscheidt <tim(at)tim-landscheidt(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Procedure for feature requests?
Date: 2009-10-02 21:48:42
Message-ID: 1254520122.27877.0.camel@jd-desktop.unknown.charter.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 2009-10-02 at 21:37 +0000, Tim Landscheidt wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
> > [...]
> >> Suppose the feature request was not a trivial one, but
> >> maybe a "DEPENDS ON <object>" clause for "CREATE FUNCTION"
> >> to allow PostgreSQL to deny requests to drop a table/view/
> >> function that is needed by a function - where would I pro-
> >> pose that?
>
> > On -hackers, just like any other feature request, trivial or not.
>
> Thanks. Any particular form? A quick glance at the archives
> did not reveal any feature requests that were not accompa-
> nied by a patch :-).
>

There is not a specific format but a good thing to do is:

Request Feature
Provide Use Case
Provide Example syntax (if applicable)

Joshua D. Drake

> Tim
>
>
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
If the world pushes look it in the eye and GRR. Then push back harder. - Salamander

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-10-02 21:55:57 Re: Limit of bgwriter_lru_maxpages of max. 1000?
Previous Message Tim Landscheidt 2009-10-02 21:48:14 Re: Procedure for feature requests?