Re: TODO list

From: David Felstead <David(dot)Felstead(at)colesmyer(dot)com(dot)au>
To: Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: "'Andrew Dunstan'" <andrew(at)dunslane(dot)net>
Subject: Re: TODO list
Date: 2003-12-17 22:53:46
Message-ID: DB52470712E0D611889E0002A52CE3080537B562@ariel.colesmyer.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
InterScan_Disclaimer.txt text/plain 432 bytes

Browse pgsql-hackers by date

  From Date Subject
Next Message David Felstead 2003-12-17 22:59:40 Re: TODO list
Previous Message Tom Lane 2003-12-17 22:45:39 Re: TODO list