Re: Strange RETURN NEXT behaviour in Postgres 8.0
This is a discussion on Re: Strange RETURN NEXT behaviour in Postgres 8.0 within the pgsql Hackers forums, part of the PostgreSQL category; --> "Sergey E. Koposov" <math@sai.msu.ru> writes: > But concerning to the added columns, I can say that before the column ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-11-2008, 03:44 AM
| ||||
| ||||
 Re: Strange RETURN NEXT behaviour in Postgres 8.0 "Sergey E. Koposov" <math@sai.msu.ru> writes: > But concerning to the added columns, I can say that before the column errbox > didn't, and I revealed the problems began after adding it (together with > index creation on that column). Does starting a new backend session make the problem go away? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match      |
Linear Mode
