Skip site navigation (1) Skip section navigation (2)

Re: libpq5 8.3 breaks 8.2 compatibility with encodings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martin Pitt <martin(at)piware(dot)de>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: libpq5 8.3 breaks 8.2 compatibility with encodings
Date: 2007-10-12 16:02:44
Message-ID: 28378.1192204964@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Martin Pitt <martin(at)piware(dot)de> writes:
> However, if I use 8.2 programs with the 8.3 library, things start to
> become weird:

>   $ # kill postgres instance
>   $ rm -rf /tmp/x; LC_ALL=3Den_US.UTF-8 /usr/lib/postgresql/8.2/bin/initdb =
> --encoding UTF8 -D /tmp/x

Does anything other than initdb get weird?

For the most part I believe it's the case that libpq's idea of the enum
values is independent of the backend's.  I think the issue here is that
initdb is (mis) using libpq's pg_char_to_encoding, etc, and combining
those functions with its own idea of the meanings of the enum values.

Maybe we should stop exporting pg_char_to_encoding and so on from libpq,
though I wonder if that would break any clients.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Martin PittDate: 2007-10-12 16:18:45
Subject: Re: libpq5 8.3 breaks 8.2 compatibility with encodings
Previous:From: Tom LaneDate: 2007-10-12 15:50:35
Subject: Re: libpq5 8.3 breaks 8.2 compatibility with encodings

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group