I wrote:
> "Daniel Grace" <thisgenericn...@gmail.com> writes:
>> One such file (contents listed below, admittably not 100% useful without a
>> full schema and data) makes a bunch of alterations to a table but fails when
>> it reaches CLUSTER:
>> psql:D:/SVN/wings/wings/branches/devpg/db/lib/course.sql:38: ERROR: index
>> 178138 does not belong to table 176177
>> However, this failure only occurs if the file is wrapped in a transaction
>> block. Outside of a transaction block, it works fine.
> I wonder if the issue is that the planner thinks the index isn't usable
> yet because of HOT-chain issues.
On closer inspection this seems to be just insufficient consideration of
corner cases. We can handle it with a pretty trivial fix in
plan_cluster_use_sort. Thanks for the bug report!
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
