Re: Bug #827: pg_dump in 7.3 can't dump 7.1 db

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #827: pg_dump in 7.3 can't dump 7.1 db
Date: 2002-12-01 16:43:17
Message-ID: 18653.1038760997@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> Further investigation seems to indicate this is caused by the cast of
> oprcode to oid at line 1687 of pg_dump.c ("oprcode::oid"). It results in
> the output not being named 'oprcode'. I am a little surprised it's not a
> problem in the 7.3 code branch as well - but maybe it is?

Ah --- probably back in 7.1, the backend's automatic output-column-name
selector was not bright enough to dig down inside typecasts.
Your patch (assign the column name explicitly) is a good one.

This brings up a more general issue, which is that we need to test
pg_dump against old backend versions as well as new ones. I had had
a private "todo" item to run some tests of that sort for 7.3, but never
got 'round to it.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2002-12-01 16:47:23 Re: Bug #828: psql in 7.3 can't talk to 7.1 backends
Previous Message Tom Lane 2002-12-01 16:35:05 Re: Bug #826: opaque->internal translation required for 7.2 dumps