Re: TODO list - Mailing list pgsql-hackers

From David Felstead
Subject Re: TODO list
Date
Msg-id DB52470712E0D611889E0002A52CE3080537B562@ariel.colesmyer.com.au
Whole thread Raw
In response to TODO list  (Marko Zmak <xmak@sharanet.org>)
List pgsql-hackers
Andrew Dunstan wrote:

>Before we even get there we need agreement on exactly what it means :-)
>
>Seems like the best place for the settings might be pg_hba.conf.
>
>Say we have a new keyword "limit" there. Here are the possibilities (I
>think):

<snip>

First post (unlurking) here, so just a minor contribution.  I think that
there is already a LIMIT keyword, ala:

http://www.postgresql.org/docs/7.4/static/queries-limit.html

Since this is more or less a privileges issue, would it be reasonable to
extend the GRANT/REVOKE style syntax (with a different keyword, of course)
to allow this parameter to be set, just for consistencies sake? This would
also allow the sysadmin to limit connections on groups as well, if
necessary.

I'm not sure how you would structure a GRANT/REVOKE style query to include
a numeric parameter so it doesn't look completely out of place, so it's just
an idea...

Best regards,

-David Felstead

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: TODO list
Next
From: "Robert Bedell"
Date:
Subject: Re: OLAP CUBE/ROLLUP Operators and GROUP BY grouping sets