From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | aravinth(dot)s(at)vortexindia(dot)co(dot)in |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14597: Delay in query execution |
Date: | 2017-03-22 15:23:11 |
Message-ID: | 32763.1490196191@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
aravinth(dot)s(at)vortexindia(dot)co(dot)in writes:
> The following bug has been logged on the website:
> Bug reference: 14597
> Logged by: Aravinth Sundaram
> Email address: aravinth(dot)s(at)vortexindia(dot)co(dot)in
> PostgreSQL version: Unsupported/Unknown
> Operating system: Windows Server 2008
> Description:
> A simple delete query performed on a table with 3000 rows took almost 2 hrs
> and 40 mins. The table was vacuumed before executing the query. SQL Server
> was running in the same machine. What could be the reason for the delay?
This is (a) probably not a bug, and (b) entirely undiagnosable from
the amount of information you've given.
For help with asking answerable questions, see
https://wiki.postgresql.org/wiki/Slow_Query_Questions
(But, FWIW, a common reason for slow deletes is a foreign key
referencing this table, where the referencing column is unindexed.
Or maybe the delete was just blocked on somebody's exclusive lock?)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-03-22 15:31:49 | Re: BUG #14596: False primary/unique key constraint violations |
Previous Message | bricklen | 2017-03-22 14:50:48 | Re: BUG #14596: False primary/unique key constraint violations |