Re: Name of encodings: in which system catalog?

Lists: pgsql-general
From: Stephane Bortzmeyer <bortzmeyer(at)nic(dot)fr>
To: pgsql-general(at)postgresql(dot)org
Subject: Name of encodings: in which system catalog?
Date: 2002-07-02 19:38:10
Message-ID: 200207021938.g62JcA09014914@ludwigV.sources.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general


When I SELECT encoding FROM pg_database, I get a number. When I type \l,
encodings are displayed as a human-readable string. I do not find where these
strings are stored. I've read "PostgreSQL 7.2.1 Developer's Guide", Chapter 3.
"System Catalogs" but without result.

PS: this is because I wonder why I can enter composed characters like ç or é
when the database is in SQL_ASCII but not when it is UNICODE.


From: frbn <frbn(at)efbs-seafrigo(dot)fr>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Name of encodings: in which system catalog?
Date: 2002-07-03 08:16:38
Message-ID: 3D22B2E6.8060003@efbs-seafrigo.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general

try psql -E and retype \l

Stephane Bortzmeyer wrote:
> When I SELECT encoding FROM pg_database, I get a number. When I type \l,
> encodings are displayed as a human-readable string. I do not find where these
> strings are stored. I've read "PostgreSQL 7.2.1 Developer's Guide", Chapter 3.
> "System Catalogs" but without result.
>
> PS: this is because I wonder why I can enter composed characters like ç or é
> when the database is in SQL_ASCII but not when it is UNICODE.


From: Stephane Bortzmeyer <bortzmeyer(at)nic(dot)fr>
To: frbn <frbn(at)efbs-seafrigo(dot)fr>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Name of encodings: in which system catalog?
Date: 2002-07-03 16:45:02
Message-ID: 20020703164502.GA12227@nic.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general

On Wed, Jul 03, 2002 at 10:16:38AM +0200,
frbn <frbn(at)efbs-seafrigo(dot)fr> wrote
a message of 19 lines which said:

> try psql -E and retype \l

Oh, yes, I always forgot this very useful trick. Thanks. For thoses
interested, encodings are not stored in a table but in a function.