On Mon, Aug 27, 2012 at 1:56 PM, Maximilian Tyrtania <lists@xxxxxxxxxxxxxx> wrote: >> It might be a broken index issue. Please show the EXPLAIN for these queries. > > It was. I had an index like this: > > CREATE INDEX idx_firmen_iskunde_index > ON firmen > USING btree > (f_firmen_iskunde(firmen.*)); > > Dropping and recreating it fixed it. Note that having such functional index you are risking to face similar oddities again after you modify the function. You need to manually reindex all the indexes that uses the function after it has been modified. To PG hackers. Are there any plans to add dependencies that will resolve such issues somehow? -- Sergey Konoplev a database architect, software developer at PostgreSQL-Consulting.com http://www.postgresql-consulting.com Jabber: gray.ru@xxxxxxxxx Skype: gray-hemp Phone: +79160686204 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
