Re: Cancel/Kill backend functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: Neil Conway <neilc(at)samurai(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Cancel/Kill backend functions
Date: 2004-05-28 05:30:01
Message-ID: 14714.1085722201@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> With this comment, I take it you'd disagree with my recoding of
> TransactionIdIsCurrentTransactionId().

> The current code has to scan only the xid's in each PGPROC struct.
> However I had to rewrite it to peek at pg_subtrans, and this is done
> while the SInvalLock is share-locked. pg_subtrans may need to do some
> I/O to get the data, and there could be multiple queries, depending on
> the nesting level.

You're right, I think that's really awful :-(

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Sean Chittenden 2004-05-28 05:48:41 Small doc patch for area() function...
Previous Message Alvaro Herrera 2004-05-28 05:14:55 Re: Cancel/Kill backend functions