From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | boris(at)folgmann(dot)de, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #867: CLUSTER does not rebuild referential |
Date: | 2003-01-08 21:28:56 |
Message-ID: | 1042061336.42584.13.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)postgresql(dot)org wrote:
> Boris Folgmann (boris(at)folgmann(dot)de) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> CLUSTER does not rebuild referential integrity triggers
>
> Long Description
> I've got the following behaviour using pgsql 7.2.2 on Linux:
>
> When clustering a table with CLUSTER I get
> NOTICE: DROP TABLE implicitly drops referential integrity trigger from table .... for every RI_ConstraintTrigger. The bad thing is that the Trigger is not being reconstructed when the CLUSTER is finished.
>
>
> Sample Code
> \d table_with_ri_triggers
> cluster some_index on table_with_ri_triggers
> \d table_with_ri_triggers
>
> -> see that ri_triggers are vanished.
>
>
> No file was uploaded with this report
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-01-08 23:18:35 | Re: More SSL patches |
Previous Message | pgsql-bugs | 2003-01-08 20:21:25 | Bug #867: CLUSTER does not rebuild referential integrity triggers |