Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling
Date: 2004-08-24 14:31:13
Message-ID: 3252.1093357873@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Richard Huxton <dev(at)archonet(dot)com> writes:
> ... Don't forget having to deal with a backend dying without being able to
> decrement the count (not my idea, Bruce (iirc) mentioned it last time
> this was discussed). I think at the least you'd need a
> max-trans-id-with-lock number stored next to the count so that in the
> event of backend crashes the lock will eventually be released.

No, because the whole table would simply be flushed upon backend crash.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2004-08-24 20:41:41 pgsql-server: Allow second and subsequent names in a qualified (dotted)
Previous Message Alvaro Herrera 2004-08-24 14:09:32 Re: pgsql-server: Update that 8.0 will support MS Win

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-08-24 14:35:34 Re: 8.0 beta 1 on linux-mipsel R5900
Previous Message Alvaro Herrera 2004-08-24 14:09:32 Re: pgsql-server: Update that 8.0 will support MS Win