From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Richard Plotkin <richard(at)richardplotkin(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Disk filling, CPU filling, renegade inserts and deletes? |
Date: | 2005-04-23 19:50:56 |
Message-ID: | 14610.1114285856@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Richard Plotkin <richard(at)richardplotkin(dot)com> writes:
> Thanks for your responses this morning. I did the select relname, and
> it returned 0 rows. I do have one function that creates a temp table
> and fills it within the same transaction. I'm pasting it below.
> Perhaps the "ON COMMIT DROP" is causing problems, and I need to drop
> the table at the end of the function instead of using ON COMMIT DROP?
Well, I think we can conclude that the function is pushing way more
data into the temp table than you expect. I am wondering if that loop
in the middle of the function is turning into an infinite loop --- could
it be finding some sort of cycle in your page data? You might want to
add some RAISE NOTICE commands to the loop so you can track what it's
doing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Fradkin | 2005-04-23 20:18:36 | flattening the file might work for me here is the analyze. |
Previous Message | Richard Plotkin | 2005-04-23 18:37:30 | Re: Disk filling, CPU filling, renegade inserts and deletes? |