| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Uwe Schroeder <uwe(at)oss4u(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: virtualidx exclusive lock |
| Date: | 2009-11-09 11:36:34 |
| Message-ID: | 407d949e0911090336h273fcf0anff6d7067aa233672@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 9, 2009 at 7:38 AM, Uwe Schroeder <uwe(at)oss4u(dot)com> wrote:
> What I noticed is when I look at pg_locks, pretty much all of the processes being idle in transaction have an exclusive lock of locktype "virtualidx".
It's "virtualxid" as in "virtual transaction id" and hopefully more
than pretty much all have a lock of this type -- *all* transactions
start with a lock on their own transaction id and hold it until they
finish. That's how other transactions wait for a transaction to
finish, by attempting to get a lock on the transaction id of the
transaction they're waiting on.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Jas | 2009-11-09 12:03:20 | Re: Donwload location for PostgreSQL version 8.2.7 |
| Previous Message | Arjen Nienhuis | 2009-11-09 11:33:10 | Re: Donwload location for PostgreSQL version 8.2.7 |