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

RE: Default encoding in database

From: "Jacob Vennervald Madsen" <jvm(at)gopinocchio(dot)com>
To: "Karel Zak" <zakkr(at)zf(dot)jcu(dot)cz>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: RE: Default encoding in database
Date: 2001-08-30 09:04:39
Message-ID: 19514C7E64E4FA4FBEEC9BA3CB3376FD17B686@gopinocchio-sbs.gopinocchio.local (view raw, whole thread or download thread mbox)
Lists: pgsql-general
If I do rebuild it with initdb will I still have all my data?


-----Original Message-----
From: Karel Zak [mailto:zakkr(at)zf(dot)jcu(dot)cz]
Sent: 30. august 2001 11:03
To: Tatsuo Ishii
Cc: Jacob Vennervald Madsen; pgsql-general(at)postgresql(dot)org
Subject: Re: Default encoding in database

On Thu, Aug 30, 2001 at 05:28:16PM +0900, Tatsuo Ishii wrote:
> > > How does the output from "psql -l" look like?
> >          List of databases
> >   Database  |  Owner   | Encoding
> > ------------+----------+-----------
> >  template0  | postgres | SQL_ASCII
> >  template1  | postgres | SQL_ASCII
> > Jacob
> I don't know why your template1 DB's encoding is SQL_ASCII, but you
> need to change the encoding of the DB anyway.
> try:
> psql -c "update pg_database set encoding = 7 where datname =
> 'template1'" template1

IMHO more careful is re-build it by initdb with option -E LATIN1.


 Karel Zak  <zakkr(at)zf(dot)jcu(dot)cz>
 C, PostgreSQL, PHP, WWW,,


pgsql-general by date

Next:From: Francesco CasadeiDate: 2001-08-30 09:05:23
Subject: Re: [SQL] getting the oid for a new tuple in a BEFORE trigger
Previous:From: Karel ZakDate: 2001-08-30 09:02:54
Subject: Re: Default encoding in database

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