Re: Small patch to replace 'idle' by 'trans' if transaction is still open
От | Philip Warner |
---|---|
Тема | Re: Small patch to replace 'idle' by 'trans' if transaction is still open |
Дата | |
Msg-id | 3.0.5.32.20001012021247.021dd100@mail.rhyme.com.au обсуждение исходный текст |
Ответ на | Re: Small patch to replace 'idle' by 'trans' if transaction is still open (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Small patch to replace 'idle' by 'trans' if transaction is still open
|
Список | pgsql-patches |
At 10:54 11/10/00 -0400, Tom Lane wrote: >Philip Warner <pjw@rhyme.com.au> writes: >> Any chance of showing if anything has been updated in the TX? > >Hmm ... SharedBufferChanged would probably do as a proxy for that ... >not sure if it's a good idea though. The idea was to indicate if the process is likely to be causing a locking problem - but now I think about it, a more useful pice of information would be if any tables/rows/whatever are locked in such a way that another user might be prevented from doing an update. Is this possible? I would maintain that if possible, it is useful to distinguish logical 'read-only' transactions from TXs that might lock another user. ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 0500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/
В списке pgsql-patches по дате отправления: