Re: [HACKERS] pg_upgrade problem

> I am updating a database from 6.4 to 6.5. This statement was produced
> by 6.4.2's pg_dumpall but is not accepted by 6.5:
>
> CREATE RULE "rtest_v1_upd" AS ON UPDATE TO "rtest_v1"
> DO INSTEAD UPDATE rtest_t1 SET "a" = new."a", "b" = new."b"
> WHERE "a" = current."a";
>
> ERROR: current: Table does not exist.
>
> This rule is part of the regression tests and it seems that `current' has
> now been changed to `old'. Apart from the error messages that occur
> as the script flows past (too fast to read) pg_upgrade does not
> offer any explanations; it merely says that psql failed to run the
> script, which is contrary to what the user (me) thinks he has just seen.

Yikes. I forgot to disable pg_upgrade in this release. I don't think
it is going to work because the on-disk tuple structures has changed for
MVCC? Vadim, an I correct?

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026