From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
Cc: | Christopher Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Another small bug (pg_autovacuum) |
Date: | 2003-09-11 22:25:32 |
Message-ID: | 2379.1063319132@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Matthew T. O'Connor" <matthew(at)zeut(dot)net> writes:
> On Thu, 2003-09-11 at 17:11, Tom Lane wrote:
>> "Matthew T. O'Connor" <matthew(at)zeut(dot)net> writes:
>>> I designed it that way. It was my understanding that all of the system
>>> tables pg_class etc... are shared tables, available in all databases,
>>> but actually stored as only one central set of real tables.
>>
>> Only the tables marked "relisshared" in pg_class (currently pg_shadow,
>> pg_group, pg_database, and their indexes and toast tables) are shared
>> across a cluster. The rest have separate copies per-database.
> hrm.... OK. Patch forthcoming....
BTW, I am not sure it is a good idea to suppress "redundant" vacuuming
of shared tables in the first place. The trouble with doing so is that
if you only vacuum pg_shadow through template1, then only template1 will
ever have up-to-date statistics about it. That's not good.
You might be able to get away with doing actual vacuums only through
template1, and doing just ANALYZEs every so often in other DBs.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2003-09-11 22:28:21 | Re: Problem with function permission test in a view |
Previous Message | Tom Lane | 2003-09-11 22:20:33 | Re: massive quotes? |