Skip site navigation (1) Skip section navigation (2)

Re: Small patch to replace 'idle' by 'trans' if transaction is still open

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: Christof Petig <christof(dot)petig(at)wtal(dot)de>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Small patch to replace 'idle' by 'trans' if transaction is still open
Date: 2000-10-14 16:27:50
Message-ID: 2521.971540870@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> Sounds like a good start. But would it be possible/desirable for a utility
> program to map the lock manager tables directly? 

The utility program would have to be able to attach to the shared memory
segments holding the locktable and associated spinlocks.  And if you
did it that way, you couldn't inspect the locktable remotely without
duplicating a bunch more postmaster/backend code.  Offhand it seems to
me that "start an additional backend and use it to look at the
locktable" is the best way to approach this.

This does raise an interesting point though: do we need any security on
this new SHOW command?  Like, say, only allow it to superusers?

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Vadim MikheevDate: 2000-10-14 20:19:17
Subject: WAL status & todo
Previous:From: Philip WarnerDate: 2000-10-14 12:27:41
Subject: Re: Small patch to replace 'idle' by 'trans' if transaction is still open

pgsql-patches by date

Next:From: Tom LaneDate: 2000-10-14 16:50:44
Subject: Re: src/backend/commands/sequence.c
Previous:From: Philip WarnerDate: 2000-10-14 12:27:41
Subject: Re: Small patch to replace 'idle' by 'trans' if transaction is still open

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group