Re: WIN1250 as server encoding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIN1250 as server encoding
Date: 2004-09-15 15:21:28
Message-ID: 4038.1095261688@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:
> Some people have requested to add WIN1250 as an allowed server encoding.
> So far, the order of the encoding numbers determined which ones were
> client-only, so in order not to renumber the encodings, I could only
> come up with the attached ugly solution. If no one thinks of a better
> one, we'll go with that.

Can't we just renumber them?

AFAIR, the only place where these numbers are stored is in
pg_database.datencoding, so only the server-encoding values are frozen
in any meaningful sense. You could rearrange the numbers currently
assigned to client encodings to preserve the range property.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message G u i d o B a r o s i o 2004-09-15 16:04:37 PG_exception_stack
Previous Message Andrew Dunstan 2004-09-15 15:19:41 Re: PL/PgSQL "bare" function calls