| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Function won't complete |
| Date: | 2002-04-26 22:54:26 |
| Message-ID: | 12718.1019861666@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"Josh Berkus" <josh(at)agliodbs(dot)com> writes:
> I am currently testing a massive data update function, which takes a
> large amount of raw data (in 3 tables comprising over 2 million records
> total) and organizes and cleans that data in a series of successive
> steps for the final relational database.
> The problem is, it doesn't complete. About 1/3 of the way in to the
> data updates, postgres gets stuck in an endless cycle of recycling
> transaction logs and child processes and won't finish (current longest
> abort time is 37 minutes).
You sure it's not just a programming error (the proverbial unconstrained
join, for example)?
Without seeing the query(s) I doubt we can help you much.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eduardo Gargiulo | 2002-04-27 04:28:55 | pg_shadow password |
| Previous Message | Tom Lane | 2002-04-26 22:43:41 | Re: Wierd query behaviour |