Re: lock listing - Mailing list pgsql-patches

From nconway@klamath.dyndns.org (Neil Conway)
Subject Re: lock listing
Date
Msg-id 20020731192332.GA27143@klamath.dyndns.org
Whole thread Raw
In response to Re: lock listing  (Rod Taylor <rbt@zort.ca>)
Responses Re: lock listing  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: lock listing  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
On Wed, Jul 31, 2002 at 03:15:56PM -0400, Rod Taylor wrote:
> On Wed, 2002-07-31 at 14:47, Neil Conway wrote:
> > On Wed, Jul 31, 2002 at 02:34:19PM -0400, Bruce Momjian wrote:
> > > Yes, I think that would be the way to go, or look at the stat functions
> > > that return tuple sets and use those.  That may be a cleaner solution.

[...]

> Lastly, it'll show up in \dS if it's a sudo table.  The function is
> buried in thousands of \df results.

I'm confused: I thought that Bruce was suggesting that I change the
lock status functions to be similar to the stats functions (i.e. one
function for every piece of data and a view that pulls them all
together).

There's no problem with wrapping a view over the table function -- but
IMHO using 5 different functions when one would suffice is just ugly.

Cheers,

Neil

--
Neil Conway <neilconway@rogers.com>
PGP Key ID: DB3C29FC

pgsql-patches by date:

Previous
From: Rod Taylor
Date:
Subject: Re: lock listing
Next
From: Tom Lane
Date:
Subject: Re: lock listing