Can anyone tell me whether the bug where the tgconstrrelid column of the
pg_triggers catalogue was ever fixed ("[BUG?] tgconstrrelid doesn't
survive a dump/restore" -
http://archives.postgresql.org/pgsql...msg00720.php)? I am
finding some effects of this in my database, but that could be left over
from pg 7.2 (we recently switched to 7.3.) What I am really asking, is if
I chop-and-hack it back together, can I be reasonably sure it will stay
in one piece?

Thanks,

Misha Gale
--
Misha Gale
mishagale (AT) fastmail (DOT) fm

--
http://www.fastmail.fm - Sent 0.000002 seconds ago

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org

On Wed, 8 Oct 2003, Misha Gale wrote:

Yes. I believe the actual bug was fixed somewhere in 7.2 time period (
I don't remember precisely), but any dumps from before that will not have
the information.

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match