Re: lock listing

From: nconway(at)klamath(dot)dyndns(dot)org (Neil Conway)
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: lock listing
Date: 2002-07-23 22:47:18
Message-ID: 20020723224718.GA11484@klamath.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On Tue, Jul 23, 2002 at 05:52:39PM -0400, Bruce Momjian wrote:
> I agree with Peter that it is better to rename it pg_lock*. The show
> isn't needed and it makes it look more like our other system info
> tables.

Well, it's not a system info table -- it's a built-in function, and I'm
not aware of any naming conventions for those. Personally, I find it a
bit confusing to do:

SELECT * FROM pg_tables;
SELECT * FROM pg_class;
/* ... */
SELECT * FROM pg_locks();

However, I'm not really worried about the name, so I've changed it
to pg_locks() -- a revised patch is attached.

Cheers,

Neil

--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC

Attachment Content-Type Size
lock-listing-13.patch text/plain 17.1 KB

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2002-07-23 23:13:52 Re: Fk fix for noaction update/delete
Previous Message Bruce Momjian 2002-07-23 22:18:16 Re: Table Function API doc patch