From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tobias Brox <tobixen(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: locking issue on simple selects? |
Date: | 2010-09-15 19:21:18 |
Message-ID: | 23278.1284578478@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Tobias Brox <tobixen(at)gmail(dot)com> writes:
> Well - I thought so, we have a logging script that logs the content of
> the pg_locks table, it didn't log anything interesting but it may be a
> problem with the script itself. It does an inner join on
> pg_locks.relation = pg_class.oid but when I check now this join seems
> to remove most of the rows in the pg_locks table. Does it make sense
> at all to join pg_class with pg_locks? I will ask the sysadm to
> change to an outer join as for now.
There are lots of locks that are not tied to a specific table, so an
inner join is definitely bad. You could use an outer join to annotate
rows that do correspond to table locks, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2010-09-15 19:28:24 | Re: locking issue on simple selects? |
Previous Message | Tobias Brox | 2010-09-15 19:07:24 | Re: locking issue on simple selects? |