From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mark Kirkwood <markir(at)coretech(dot)co(dot)nz> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Display Pg buffer cache (WIP) |
Date: | 2005-03-08 14:55:56 |
Message-ID: | 6072.1110293756@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Mark Kirkwood <markir(at)coretech(dot)co(dot)nz> writes:
> Tom Lane wrote:
>> I would rather see this as a contrib module. There has been *zero*
>> consensus that we need this in core, nor any discussion about whether
>> it might be a security hole.
> Hmmm, I guess my motivation for thinking it might be useful in core was
> that it was similar to 'pg_locks' and 'pg_stats', i.e. exposing some
> internals in a convenient queryable manner (useful for problem solving).
One reason for making it contrib is that I don't think you've got it
entirely right yet, and there will be several iterations before it
settles down. In a contrib module that is no problem, in core it's a
forced initdb each time.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Brown | 2005-03-08 17:40:02 | CC Date format code defaults to current centry |
Previous Message | Pavel Stehule | 2005-03-08 09:18:36 | Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables for |