| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Autovacuum in the backend |
| Date: | 2005-06-16 03:42:17 |
| Message-ID: | 42B0F519.30604@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Alvaro Herrera wrote:
>A question for interested parties. I'm thinking in handling the
>user/password issue by reading the flat files (the copies of pg_shadow,
>pg_database, etc).
>
>The only thing that I'd need to modify is add the datdba field to
>pg_database, so we can figure out an appropiate user for vacuuming each
>database.
>
>What do people think?
>
>
I probably don't understand all the issue involved here but reading
pg_shadow by hand seems problematic. Do you constantly re-read it?
What happens when a new user is added etc....
Can't autovacuum run as a super-user that can vacuum anything?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Russell Smith | 2005-06-16 03:45:04 | Re: Autovacuum in the backend |
| Previous Message | Alvaro Herrera | 2005-06-16 02:54:58 | Re: Autovacuum in the backend |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Russell Smith | 2005-06-16 03:45:04 | Re: Autovacuum in the backend |
| Previous Message | Tom Lane | 2005-06-16 03:27:36 | Re: Two-phase commit |