Re: pg_dump failure, can't get data out...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Larry Rosenman <ler(at)lerctr(dot)org>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump failure, can't get data out...
Date: 2001-08-27 04:16:15
Message-ID: 3165.998885775@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Offhand I don't see a related change in pg_dump in
> recent times, so it probably isn't necessarily an upgrade related issue,
> it might be an inconsistent schema.

The proximate cause is that I changed pg_index.indproc from plain "oid"
to "regproc" a week ago, so the output format is different. It seemed
like a good idea at the time ...

I have hacked pg_dump to force the output format back to oid, but I'm
sorta thinking that the schema change was ill-advised because it's
likely to break other applications that look at indproc. Should we
change the column back to oid?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Karel Zak 2001-08-27 07:26:17 Re: [PATCHES] encoding names
Previous Message Bruce Momjian 2001-08-27 04:09:03 Pgsql roadmap