From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: db encoding |
Date: | 2003-10-06 19:05:53 |
Message-ID: | 3F81BD11.8040305@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 |
Peter Eisentraut wrote:
>About pg_encoding. There is currently no way to tell whether an encoding
>exists. Normally you would put this kind of thing into a system table,
>but doing that is a bit tricky with the encodings. I would like to see
>pg_encoding go, so let's hear what information people need and give them a
>direct way to access it.
>
You need the encoding ID before you have a system to have tables in - while you are running the bootstrap code - unless things change.
That isn't to say that putting the available encodings into a table isn't a good idea, though.
I'm not sure I see anywhere in the docs a ref to what encodings are available, or how to find that out - if I haven't missed it that's something to be remedied.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | markw | 2003-10-06 19:15:53 | Re: More Prelimiary DBT-2 Test Results with PostgreSQL |
Previous Message | Tom Lane | 2003-10-06 18:49:51 | Re: Open 7.4 items |
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2003-10-06 19:42:27 | Re: db encoding |
Previous Message | Peter Eisentraut | 2003-10-06 18:30:47 | Re: db encoding |