ld be addressed as a bug.
Thanks for your help,
Keith Browne
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
lishes the connection to the database.
It would appear that psql is doing something right here which we have
had to go out of our way to get with psycopg.
Keith Browne
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
ll fix the complaint or not.
It sounds like this could work for us, if it would disable sequential
searches into a table which grows from 0 to >60,000 rows in one session.
Is breaking and re-establishing the database session the best
workaround, or is there a better way to provide a hint
