Andreas Pflug wrote:
> Merlin Moncure wrote:
> >>>3) Allow GRANT/REVOKE permissions to be applied to all schema
> >
> > objects
> >
> >>>with one
> >>
> >>Maybe this is "apply schema changes to several objects with one
> >>command". This seems reasonable.
> >
> >
> > Well, I don't know. IMO,
Merlin Moncure wrote:
3) Allow GRANT/REVOKE permissions to be applied to all schema
objects
with one
Maybe this is "apply schema changes to several objects with one
command". This seems reasonable.
Well, I don't know. IMO, what I would really like to see is for various
database objects to inheri
> > 3) Allow GRANT/REVOKE permissions to be applied to all schema
objects
> > with one
>
> Maybe this is "apply schema changes to several objects with one
> command". This seems reasonable.
Well, I don't know. IMO, what I would really like to see is for various
database objects to inherit permi
OK guys - i think I go for #3:
Allow GRANT/REVOKE permissions to be applied to all schema objects with
one
cheers,
Matthias
Am 18.01.2005 um 20:47 schrieb Tom Lane:
Matthias Schmidt <[EMAIL PROTECTED]> writes:
These are the things I'm interested in:
1) Allow limits on per-db/user connections
2)
Alvaro Herrera schrieb:
On Tue, Jan 18, 2005 at 08:15:10PM +0100, Matthias Schmidt wrote:
1) Allow limits on per-db/user connections
Sounds hard to do: what limits? CPU, disk?
Note that a typical server limit, the load average, will not be
portable. There's no WIN32 solution yet.
The CPU load is a
* Matthias Schmidt ([EMAIL PROTECTED]) wrote:
> 3) Allow GRANT/REVOKE permissions to be applied to all schema objects
> with one
This would be nice. I had to write a perl script to do it here. :)
It'd also be nice to be able to specify a set of permissions that will
be inheirited by newly create
Matthias Schmidt <[EMAIL PROTECTED]> writes:
> These are the things I'm interested in:
> 1) Allow limits on per-db/user connections
> 2) Allow server log information to be output as INSERT statements
> 3) Allow GRANT/REVOKE permissions to be applied to all schema objects
> with one
> 4) Allow PRE
On Tue, Jan 18, 2005 at 08:15:10PM +0100, Matthias Schmidt wrote:
> 1) Allow limits on per-db/user connections
Sounds hard to do: what limits? CPU, disk?
> 2) Allow server log information to be output as INSERT statements
Is this really needed?
> 3) Allow GRANT/REVOKE permissions to be applied
Hi *,
I have some cylcles left and like to pick up something from the TODO
list.
These are the things I'm interested in:
1) Allow limits on per-db/user connections
2) Allow server log information to be output as INSERT statements
3) Allow GRANT/REVOKE permissions to be applied to all schema objec
