Large Functions and Index Rebuild
От | Terence Gannon |
---|---|
Тема | Large Functions and Index Rebuild |
Дата | |
Msg-id | 01BF68BE.EFA66E40.tgannon@stoneboat.com обсуждение исходный текст |
Список | pgsql-general |
I'm having a lot of trouble loading plpgsql functions longer than 100-150 lines. I can nurse them in by VACUUMing, then create the function, VACUUMing again, create the next one, but it seems that eventually, I corrupt the indices on pg_proc, and I can't even VACUUM without getting something like; NOTICE: Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1092) IS NOT THE SAME AS HEAP' (1089) NOTICE: Index pg_proc_proname_narg_type_index: NUMBER OF INDEX' TUPLES (1092) IS NOT THE SAME AS HEAP' (1089) NOTICE: Index pg_proc_oid_index: NUMBER OF INDEX' TUPLES (1092) IS NOT THE SAME AS HEAP' (1089) pqReadData() -- backend closed the channel unexpectedly. This probably means the backend terminated abnormally before or while processing the request. We have lost the connection to the backend, so further processing is impossible. Terminating. Is there any way I can avoid this, or alternatively, any way of rebuilding these indices so that I can carry on? Many thanx for your help... Terry Gannon stoneboat.com
В списке pgsql-general по дате отправления: