We are trying to trace cause and potential solution of "tuple not found" error with postgres-xc. The problem happens when indexing a large file. It seems the autovaccum locks certain cache pages that the indexer tries to read. The indexing fails with "tuple not found" error.
I am sure if it qualifies as postgres or postgres-xc error. However, I was just wondering what is the recommended way to go about fixing this. Turning off the autovaccumer is really not the best of solution because then the system runs into memory usage error.
Agreed. However, the "tuple not found" error problem seems to happen with postgres as well, if not in the particular case index creation over large datasets. It would helpful to know in that scenario what are the fixes and how to avoid it in the first place.
The solution/fixes for postgres will carry over to pgxc because the low level stuff (blocks, files, indexes) etc. postgres-xc is really the same as in postgres.
you'd probably be best off finding the postgresql-xc list, as that is really a rather different system, even if it is forked from community postgresql.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
