Re: Bug #867: CLUSTER does not rebuild referential
От | Rod Taylor |
---|---|
Тема | Re: Bug #867: CLUSTER does not rebuild referential |
Дата | |
Msg-id | 1042061336.42584.13.camel@jester обсуждение исходный текст |
Ответ на | Bug #867: CLUSTER does not rebuild referential integrity triggers (pgsql-bugs@postgresql.org) |
Список | pgsql-bugs |
Upgrade to 7.3. Cluster has been redesigned to be much more user friendly -- not to mention transaction safe. On Wed, 2003-01-08 at 15:21, pgsql-bugs@postgresql.org wrote: > Boris Folgmann (boris@folgmann.de) reports a bug with a severity of 3 > The lower the number the more severe it is. >=20 > Short Description > CLUSTER does not rebuild referential integrity triggers >=20 > Long Description > I've got the following behaviour using pgsql 7.2.2 on Linux: >=20 > When clustering a table with CLUSTER I get=20 > NOTICE: DROP TABLE implicitly drops referential integrity trigger from t= able .... for every RI_ConstraintTrigger. The bad thing is that the Trigger= is not being reconstructed when the CLUSTER is finished. >=20 >=20 > Sample Code > \d table_with_ri_triggers > cluster some_index on table_with_ri_triggers > \d table_with_ri_triggers >=20 > -> see that ri_triggers are vanished. >=20 >=20 > No file was uploaded with this report >=20 >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? >=20 > http://www.postgresql.org/users-lounge/docs/faq.html --=20 Rod Taylor <rbt@rbt.ca> PGP Key: http://www.rbt.ca/rbtpub.asc
В списке pgsql-bugs по дате отправления: