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

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

Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> ie. why can't we just record the number of locks each backend has, sort
> of, and use a reference counting sort of method. Per-backend in case
> the backend dies and we need to discount those locks..?

Uh ... the interesting question is usually not "does this backend hold
any row locks", it is "is this row locked by any backends". If the
latter question is not *exceedingly* cheap to answer, at least in the
normal case where the answer is no, you don't have a workable solution,
because you'll be adding nontrivial overhead to every row update.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2004-08-24 04:59:36 Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling
Previous Message Christopher Kings-Lynne 2004-08-24 04:30:16 Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2004-08-24 04:59:36 Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling
Previous Message Tom Lane 2004-08-24 04:39:55 Re: HP-UX PA-RISC/Itanium 64-bit Patch and HP-UX 11.23 Patch