The short answer is "don't CLUSTER while the table is in live use" ...
This is kind of difficult on a busy database, more so if it's a 24x7
environment. And
unfortunately there aren't any good alternatives either.
The difference between EXECUTE and SELECT behavior here is just a chance
matter
"" <[EMAIL PROTECTED]> writes:
> Prepared SELECT/UPDATE/DELETE statements produce wrong results if executed
> while target table is being clustered.
The short answer is "don't CLUSTER while the table is in live use" ...
CLUSTER re-inserts all the rows in the table into a fresh table. This
means
The following bug has been logged online:
Bug reference: 2830
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.0, older
Operating system: Ubuntu 6.10 2.6.17-10-386, libc6 2.4-1ubuntu12
Description:Wrong results for prepared statements while cluster
