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

Re: Character set conversion

From: "Daniel T(dot) Staal" <DStaal(at)usa(dot)net>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: Character set conversion
Date: 2008-07-24 01:36:58
Message-ID: 52114.173.8.4.46.1216863418.squirrel@MageHandbook.com (view raw or flat)
Thread:
Lists: pgsql-novice
On Mon, July 21, 2008 10:16 am, Tom Lane wrote:

> It wouldn't be too hard if you don't mind running a custom Postgres
> build; but if you do, then the best answer might be to cannibalize one of
> the existing encoding names and just replace its conversion procedures.

Actually, I'd recommend not doing that.  Instead, put in your encoding as
a new encoding, and send a diff of your changes to the Postgres team.  I
bet next release it would be a supported encoding, and you would be able
to upgrade without any issues...

Daniel T. STaal

---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------


In response to

pgsql-novice by date

Next:From: Wright, GeorgeDate: 2008-07-24 12:51:13
Subject: Re: libpq question
Previous:From: Wright, GeorgeDate: 2008-07-22 20:00:32
Subject: libpq question

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