Logging seq scans

From: Guido Neitzer <guido(dot)neitzer(at)pharmaline(dot)de>
To: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Logging seq scans
Date: 2006-03-07 10:59:18
Message-ID: AF158061-88EA-42A7-8F3A-6D1B6233E453@pharmaline.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi.

Is there a way to set up logging in a way that I can see queries
which trigger seq scans? Or to log queries "taking longer than xx ms"?

Background is, that it is nearly impossible to tell, which queries
are used in my applications as they are mostly generated by the
frameworks. Yesterday I found, that one of the more often used
queries has not used an existing index and I had to use another index
for it. Nobody complained about the performance but nevertheless the
query took about 1000ms and therefore slowed down the rest of the
server ...

cug

--
PharmaLine, Essen, GERMANY
Software and Database Development

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Guido Neitzer 2006-03-07 11:05:32 Question about index usage
Previous Message Frank Church 2006-03-07 10:38:29 Re: REPOST: How to determine the table a query or a views columns come from?