Re: [HACKERS] Cache on pg_statistics - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Cache on pg_statistics
Date
Msg-id 199911250021.TAA29865@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Cache on pg_statistics  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom, let me know what caches you want on pg_statistics, or if you would
> > prefer to do it yourself, instructions are at the top of syscache.c.
> 
> AFAIK the only index we need is one on starelid + staattnum.  If you
> have the time, please put it in and teach getattstatistics() in
> backend/utils/adt/selfuncs.c to use it.  That seems to be the only
> place that reads pg_statistic.
> 
> If you wanted to include staop as a third column, then the index could
> be UNIQUE.  (We don't actually use staop at the moment, but I think it
> should be left in place for possible future use.)
> 
> vacuum.c may also need to be taught to fill the index...

Done.  Let me know how it works.  I had to add selop param to the
function getattstatistics() because I needed it to find the cache entry
because that field is in the cache.

Not sure how to test if it is working.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: lztext and parser
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] run_check problem