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.
---------------------------------------------------------------
