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
This email and any attachments may contain privileged and
confidential information and are intended for the named
addressee only. If you have received this e-mail in error,
please notify the sender and delete this e-mail immediately.
Any confidentiality, privilege or copyright is not waived or
lost because this e-mail has been sent to you in error. It
is your responsibility to check this e-mail and any
attachments for viruses.
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
