Re: Multiple Xids in PGPROC? - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Multiple Xids in PGPROC?
Date
Msg-id 409866CC.2050705@familyhealth.com.au
Whole thread Raw
In response to Re: Multiple Xids in PGPROC?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Multiple Xids in PGPROC?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Multiple Xids in PGPROC?  (Rod Taylor <rbt@rbt.ca>)
List pgsql-hackers
> I remember going through this.  Other backends will use pg_subtrans to
> know what transactions are in progress. They have to do the standard
> lookups to find the status of the parent transaction.  The backend-local
> list of xids is needed so the commit can clean up those subtransaction
> xids so that later transactions don't have to use pg_subtrans.

Is there some solution whereby the common case (99.999% of transactions 
won't be subtransactoins) is fast, and the uncommon case of being in a 
subtransaction is slower?

Chris



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Multiple Xids in PGPROC?
Next
From: Bruce Momjian
Date:
Subject: Re: Multiple Xids in PGPROC?