Re: Hung Query with No Locking Issues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Michael P(dot) McDonnell" <bzaks1424(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Hung Query with No Locking Issues
Date: 2023-05-07 21:25:34
Message-ID: 183988.1683494734@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Michael P. McDonnell" <bzaks1424(at)gmail(dot)com> writes:
> I have 2 stored procedures that need to run back to back. It could
> convert to a single one - but it's easier from a maintenance perspective to
> keep them separated.

> The first procedure effectively is
> INSERT INTO table_b () SELECT ____ FROM _table_a_;
> COMMIT;

> Total execution time - about 180s. Nothing in the pg_locks table and
> nothing in the pg_stat_activity table suggests anything is hung over.

> The second procedure mutates table_b data into table_b_collapsed
> INSERT INTO table_c () SELECT _____ FROM _table_b_ JOIN _table_b as b1_
> JOIN _table_b as b2_ JOIN _table_b as b3_, etc...;
> COMMIT;

> The first time I run my second stored procedure - it hangs for up to 8
> hours.
> If I immediately cancel and re-run the second stored procedure it runs in 2
> seconds.

Perhaps an "ANALYZE table_b" in between would help.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael P. McDonnell 2023-05-07 23:42:21 Re: Hung Query with No Locking Issues
Previous Message Laurenz Albe 2023-05-07 18:42:00 Re: Death postgres