Re: pg_buffercache tidyup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org, Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_buffercache tidyup
Date: 2006-10-22 17:52:34
Message-ID: 6710.1161539554@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> writes:
> This is probably terrible timing, but I noticed Tom had done some nice
> tidying up on pg_freespacemap to eliminate the clumsy conversion to and
> from strings. This patch does a similar thing for pg_buffercache.

Applied --- it is very late in the cycle, but minor code cleanup of
this sort seems pretty safe.

> I did wonder about not showing buffers that are invalid or not in use
> (currently displays all attributes bar the id as NULL). Comments?

I think we should leave it as-is. You can easily filter the null rows
if you don't want 'em, while they might be handy for certain sorts of
analysis. Besides, this module has already been out for one release
so we shouldn't change its API on a whim.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2006-10-22 20:25:49 Re: New CRC algorithm: Slicing by 8
Previous Message Tom Lane 2006-10-22 17:18:07 Re: Updates for vcbuild

Browse pgsql-patches by date

  From Date Subject
Next Message Thomas H 2006-10-22 23:28:32 BUG #2712: could not fsync segment: Permission denied
Previous Message Tom Lane 2006-10-22 17:18:07 Re: Updates for vcbuild