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

2004-08-23 Thread Tom Lane
Christopher Kings-Lynne <[EMAIL PROTECTED]> 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 usual

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

2004-08-23 Thread Tom Lane
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: > Just random speculation, but could we use a pg_subtrans-like setup to do > row share locks? pg_subtrans is trivial to index --- it's a linear array subscripted by TransactionId. I'm not sure what we'd do to handle row locks, which would need

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

2004-08-23 Thread Christopher Kings-Lynne
Just random speculation, but could we use a pg_subtrans-like setup to do row share locks? ie. Store them in a sort of table to avoid the problems with limited shared memory size? Chris Tom Lane wrote: Log Message: --- Rearrange pg_subtrans handling as per recent discussion. pg_subtrans