From: | Willem Buitendyk <willem(at)pcfish(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SPI_ERROR_CONNECT |
Date: | 2008-02-12 01:21:00 |
Message-ID: | 47B0F47C.7050609@pcfish.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks Tom,
I sent you a test case. The problem has since been resolved by changing
one of my functions to VOLATILE instead of IMMUTABLE. This has caught
me twice now in the last few days. I hope my learning of this will be a
little more IMMUTABLE :)
cheers,
willem
PG 8.3
Tom Lane wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | thefronny | 2008-02-12 01:55:43 | Re: type casting in 8.3 |
Previous Message | Tom Lane | 2008-02-12 00:36:05 | Re: SPI_ERROR_CONNECT |