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).
On the security front, I should have added a 'REVOKE ALL ...FROM PUBLIC'
on the view to at least control access (fortunately easy to add).
In response to
pgsql-patches by date
|Next:||From: David Fetter||Date: 2005-03-08 08:25:46|
|Subject: Re: Best practices: MERGE|
|Previous:||From: Mark Kirkwood||Date: 2005-03-08 08:24:49|
|Subject: Re: Display Pg buffer cache (WIP)|