"Michael P. McDonnell" <bzaks1424@xxxxxxxxx> 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
