Re: problems with table corruption continued
От | Brian Hirt |
---|---|
Тема | Re: problems with table corruption continued |
Дата | |
Msg-id | 017401c187ea$88ce4100$640b0a0a@berkhirt.com обсуждение исходный текст |
Ответ на | problems with table corruption continued ("Brian Hirt" <bhirt@mobygames.com>) |
Список | pgsql-hackers |
Yes, both tables had similiar functions, and the corruption was limited to only those two tables. ----- Original Message ----- From: "Tom Lane" <tgl@sss.pgh.pa.us> To: "Brian Hirt" <bhirt@mobygames.com> Cc: "Postgres Hackers" <pgsql-hackers@postgresql.org>; "Brian A Hirt" <bhirt@berkhirt.com> Sent: Tuesday, December 18, 2001 11:53 AM Subject: Re: [HACKERS] problems with table corruption continued > "Brian Hirt" <bhirt@mobygames.com> writes: > > Great, I'm also trying to create a reproducable test case for the original > > problem i reported with duplicate rows/oids/pkeys. Maybe both problems are > > a result of the same bug; i don't know. > > Were the duplicate rows all in tables that had functional indexes based > on functions similar to developer_aka_search_name? The problem we're > seeing here seems to be due to VACUUM not being able to cope with the > side effects of the SELECT inside the index function. > > regards, tom lane >
В списке pgsql-hackers по дате отправления: