Re: Long (really long) queries and not sure how to diagnose

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tony Day <tonyd(at)panztel(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Long (really long) queries and not sure how to diagnose
Date: 2010-04-30 05:32:12
Message-ID: 15083.1272605532@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Tony Day <tonyd(at)panztel(dot)com> writes:
> I am not sure what you mean by "complete query logs" but I do have a 1.3G
> Postgresql log file from the day in question.
> Is there a particular way that a "write-preventing lock" will be logged that
> I can search for in that file?

Well, other than an explicit LOCK TABLE, it'd be some sort of DDL action
on the table. CREATE INDEX, ALTER TABLE, that sort of thing. I'd try
grepping the query log for the table name and then filtering out the
easy select/insert/update/delete stuff.

regards, tom lane

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Tony Day 2010-04-30 05:45:39 Re: Long (really long) queries and not sure how to diagnose
Previous Message Tony Day 2010-04-30 05:24:38 Re: Long (really long) queries and not sure how to diagnose