From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | pgsql-admin(at)postgresql(dot)org, "Dennis Hoffman" <dennis(dot)hoffman(at)seagate(dot)com> |
Subject: | Re: postgresql question |
Date: | 2011-01-21 22:03:41 |
Message-ID: | 537.1295647421@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Dennis Hoffman <dennis(dot)hoffman(at)seagate(dot)com> wrote:
>> What can I do?
> I'd be tempted to write a script which was owned by root which
> calculated the size as desired, and grant sudo rights to merlin to
> execute that particular script as the user with rights.
Seems like a postgres-owned script would be safer. But actually
I'd suggest using contrib/dbsize rather than doing any of this.
Those functions got integrated into the core eventually, but in
7.4 they're in contrib.
(Ob-comment-you-do-realize-how-obsolete-7.4-is-dont-you)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-01-21 23:04:06 | Re: Should autovacuum do a database wide vacuum near transaction limit? |
Previous Message | John Lister | 2011-01-21 21:48:24 | Should autovacuum do a database wide vacuum near transaction limit? |