Re: BUG #2065: Problem with language conversion in pg_dump - Mailing list pgsql-bugs

From Wim Audenaert
Subject Re: BUG #2065: Problem with language conversion in pg_dump
Date
Msg-id BAY109-F25359AAB390C4CCD9CBA2AD0550@phx.gbl
Whole thread Raw
In response to Re: BUG #2065: Problem with language conversion in pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi Tom,

The problem is solved. I have reinstalled Postgres, and now pg_dump works
fine.

Best regards, and thanks for your help.

Wim


>From: Tom Lane <tgl@sss.pgh.pa.us>
>To: "Wim Audenaert" <wima85@hotmail.com>
>CC: pgsql-bugs@postgresql.org
>Subject: Re: [BUGS] BUG #2065: Problem with language conversion in pg_dump
>Date: Tue, 22 Nov 2005 23:45:58 -0500
>
>"Wim Audenaert" <wima85@hotmail.com> writes:
> > When I create a new database, this function (oid 17039 and used for utf8
> > translation) is not defined in the pg_proc table. I tried to create a
>new
> > database. The pg_proc table contains several functions, but not this
>one.
>
>Hmm, I see that utf8_to_tcvn() doesn't seem to be there anymore, but
>whether that's a bug in itself is for someone else to answer (Tatsuo?).
>What I'm wondering about is how a reference to a nonexistent function
>OID got into your new database.  There is no case in which pg_dump
>should reference a function by OID.
>
>            regards, tom lane

pgsql-bugs by date:

Previous
From: "Wim Audenaert"
Date:
Subject: Re: BUG #2065: Problem with language conversion in pg_dump
Next
From: neeraj chaudhari
Date:
Subject: unsupported frontend protocol