Re: SPI_ERROR_CONNECT
От | Tom Lane |
---|---|
Тема | Re: SPI_ERROR_CONNECT |
Дата | |
Msg-id | 13738.1202776565@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: SPI_ERROR_CONNECT (Willem Buitendyk <willem@pcfish.ca>) |
Ответы |
Re: SPI_ERROR_CONNECT
|
Список | pgsql-general |
Willem Buitendyk <willem@pcfish.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
В списке pgsql-general по дате отправления: