| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Willem Buitendyk <willem(at)pcfish(dot)ca> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: SPI_ERROR_CONNECT |
| Date: | 2008-02-12 00:36:05 |
| Message-ID: | 13738.1202776565@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Willem Buitendyk <willem(at)pcfish(dot)ca> writes:
> The problem was with the following:
> FOR current_row IN SELECT * from temp_tags_18_counted
> The select from the [temp_tags_18_counted] view is made up of 3 cross
> joins. When I simplify and remove the joins everything works. I tried
> this with some test data with only a few rows and the joins in place and
> it works too.
> In the production data table there are about 250K rows. Is it possible
> that calls to queries are colliding here or not giving each other enough
> time before being whisked around to next call in the FOR loop?
No. Please provide a test case instead of speculating. And, again,
what is the PG version?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Willem Buitendyk | 2008-02-12 01:21:00 | Re: SPI_ERROR_CONNECT |
| Previous Message | Willem Buitendyk | 2008-02-12 00:32:25 | Re: SPI_ERROR_CONNECT |