From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sören Meyer-Eppler <soerenme@google.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL 9.0.4 blocking in lseek?
Date: Mon, 31 Oct 2011 11:28:01 -0400
Message-ID: <27430.1320074881@sss.pgh.pa.us> (raw)
In-Reply-To: <4EAEAC21.5080209@google.com>
References: <4EA82B7C.1040008@google.com>
<9398.1319761978@sss.pgh.pa.us>
<4EAEAC21.5080209@google.com>
=?ISO-8859-1?Q?S=F6ren_Meyer-Eppler?= <soerenme@google.com> writes:
>> embedded in often-executed plpgsql functions, for instance. Can you
>> identify which table the lseeks are issued against?
> I wouldn't know how? I'm just using htop and "s" on the postgres process
> to find these...
Note the file number appearing in the lseeks, run "lsof -p PID" against
the backend process to discover the actual filename of that file, then
look for a match to the filename in pg_class.relfilenode.
> I have attached two of the offending execution plans. Anything obviously
> wrong with them?
What makes you say these are "offending execution plans"? Both of them
seem to be completing just fine.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, soerenme@google.com
Subject: Re: PostgreSQL 9.0.4 blocking in lseek?
In-Reply-To: <27430.1320074881@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox