On Fri, Aug 10, 2007 at 06:34:03PM +0100, Simon Riggs wrote: > On Fri, 2007-08-10 at 10:02 -0400, Brad Nicholson wrote: > > I just want to confirm that the cluster/MVCC issues are due to > > transaction visibility. Assuming that no concurrent access is happening > > to a given table when the cluster command is issued (when takes it > > visibility snapshot), it is safe to cluster that table. Correct? > > Yes, as long as pre-existing transactions do not then access the > clustered table. If they do, rows they should have seen will now not be > visible, yet you won't get an error message to say so. Don't you also need to be in a serialized transaction? -- Decibel!, aka Jim Nasby decibel@xxxxxxxxxxx EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
Attachment:
pgpKhyI9cVkZZ.pgp
Description: PGP signature
