From: | Steve Lane <slane(at)soliantconsulting(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org>, Jamie Thomas <jthomas(at)soliantconsulting(dot)com> |
Subject: | Re: Odd query behavior [urgent, but long] |
Date: | 2004-08-25 19:26:52 |
Message-ID: | BD52522C.1A680%slane@soliantconsulting.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Date: Wed, 25 Aug 2004 15:16:32 -0400
> To: Steve Lane <slane(at)soliantconsulting(dot)com>
> Cc: pgsql-admin(at)postgresql(dot)org, Jamie Thomas <jthomas(at)soliantconsulting(dot)com>
> Subject: Re: [ADMIN] Odd query behavior [urgent, but long]
>
> Steve Lane <slane(at)soliantconsulting(dot)com> writes:
>> I have enabled pretty extensive query logging on the 7.1.3 instance. What I
>> see is that certain queries take hideously long.
>
> Tell us about foreign keys associated with the table being updated?
> An UPDATE would fire triggers for both referencing and referenced keys ...
>
> I'm suspecting an unindexed or datatype-incompatible foreign key column.
Hi Tom:
Thanks. There are, unfortunately, no foreign keys or triggers anywhere in
the db that I know of. And this query is not always slow, just occasionally.
-- sgl
From | Date | Subject | |
---|---|---|---|
Next Message | Edgar Cante | 2004-08-25 21:03:28 | |
Previous Message | Tom Lane | 2004-08-25 19:16:32 | Re: Odd query behavior [urgent, but long] |