Re: updated lock listing patch

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: updated lock listing patch
Date: 2002-08-17 13:17:10
Message-ID: 200208171317.g7HDHAe12010@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


I am confused by pg_locks_result. I see it in \dS, but it doesn't
appear to display anything useful, based on the view definition. Is
this the cleanup you were talking about, Neil?

---------------------------------------------------------------------------

test=> \d+ pg_locks
View "pg_catalog.pg_locks"
Column | Type | Modifiers | Description
------------+---------+-----------+-------------
relation | oid | |
database | oid | |
backendpid | integer | |
mode | text | |
isgranted | boolean | |
View definition: SELECT pg_lock_status.relation,
pg_lock_status."database", pg_lock_status.backendpid,
pg_lock_status."mode", pg_lock_status.isgranted FROM pg_lock_status();

test=> \d+ pg_locks_result
View "pg_catalog.pg_locks_result"
Column | Type | Modifiers | Description
------------+---------+-----------+-------------
relation | oid | |
database | oid | |
backendpid | integer | |
mode | text | |
isgranted | boolean | |
View definition: SELECT 0::oid AS relation, 0::oid AS "database", 0 AS
backendpid, ''::text AS "mode", NULL::boolean AS isgranted;

---------------------------------------------------------------------------

Bruce Momjian wrote:
>
> Patch applied. Thanks.
>
> ---------------------------------------------------------------------------
>
>
> Neil Conway wrote:
> > Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> writes:
> > > This patch is an updated version of the lock listing patch.
> >
> > Woops, that patch was half-baked -- the changes to the regression
> > tests were only partially included (thanks to Alvaro Herrera for
> > pointing that out). I've attached an updated patch.
> >
> > Cheers,
> >
> > Neil
> >
> > --
> > Neil Conway <neilconway(at)rogers(dot)com>
> > PGP Key ID: DB3C29FC
>
> [ Attachment, skipping... ]
>
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> > message can get through to the mailing list cleanly
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2002-08-17 14:47:23 Re: pg_stat_reset round 4
Previous Message Bruce Momjian 2002-08-17 13:06:57 Re: [HACKERS] Better handling of parse errors