From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Yann Michel" <yann-postgresql(at)spline(dot)de>, "Josh Berkus" <josh(at)agliodbs(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: User Quota Implementation |
Date: | 2005-06-11 16:36:34 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E490E463@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Yann Michel
> Sent: 11 June 2005 09:49
> To: Josh Berkus
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] User Quota Implementation
>
>
> What do we need:
>
> - Extension of the "CREATE TABLESPACE" command:
> CREATE TABLESPACE tablespacename
> [ OWNER username ]
> [ SIZE <integer><K | M | G | T> ]
> LOCATION 'directory'
>
> - Extension of the "ALTER TABLESPACE" command:
> ALTER TABLESPACE name
> {RENAME TO newname |
> SIZE <integer><K | M | G | T> }
Wouldn't MAXSIZE be more appropriate?
> - Storage of this information in the system "tablespace" relation
>
> - Determine the actual size of a tables space
> --> Already exists in contrib/dbsize/dbsize.c
A patch was recently submitted by Andreas Pflug to move those functions
into the backend permanently.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-11 16:54:12 | Re: CPU-intensive autovacuuming |
Previous Message | Tom Lane | 2005-06-11 16:25:32 | Re: proposed TODO: non-locking CREATE INDEX / REINDEX |