Re: How do I measure user disk usage on Postgresql table?

From: "Dave" <withheld(at)nospam(dot)thanks>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: How do I measure user disk usage on Postgresql table?
Date: 2008-04-18 14:48:07
Message-ID: c8a90$4808b4a7$453dce02$19197@FUSE.NET
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Richard Huxton" <dev(at)archonet(dot)com> wrote in message
news:4808991E(dot)7060501(at)archonet(dot)com(dot)(dot)(dot)
> Dave wrote:
>> Lets say I have a Postgresql table where I store uploaded data for
>> all users, identified by user_id column. Is it possible to run a
>> query to measure the storage a user is consuming?
>
> Not really. You could get the size of the whole table with
> pg_relation_size() and then estimate a user's share by seeing what % of
> rows have their user-id.
>
> If it's the sort of thing you'll be checking constantly, then I'd keep a
> summary table up-to-date using triggers instead.
>
> Oh - if you're going to be asking questions regularly then you'll probably
> get more answers if you have a valid email address.
>
> --
> Richard Huxton
> Archonet Ltd
>
> --
Richard,

Thanks for the answer.

So what is the proper way of managing user quota on database (apart from
having separate table for each)?

> Oh - if you're going to be asking questions regularly then you'll probably
> get more answers if you have a valid email address.
Isn't that asking for spam (and I know the answer to that)? Why would it
matter for someone to answer my post based on my email address, if the
discussion is going over the groups? One might just as well use:
fake_user(at)gmail(dot)com(dot) At least I'm forthcoming by making it obvious that my
email address is not real. Just a thought.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Enke 2008-04-18 14:49:54 Re: good experience with performance in 8.2 for multi column indexes
Previous Message Tom Lane 2008-04-18 14:43:59 Re: good experience with performance in 8.2 for multi column indexes