Re: BUG #8255: encoding latin1

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: gabriel(dot)ct(at)santamonicace(dot)com(dot)br
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8255: encoding latin1
Date: 2013-06-27 08:06:05
Message-ID: CAB7nPqTdFcQYAmvqX-d_8ZMujtN0_d3R1HX0H5uepF+wLMb0KQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jun 26, 2013 at 9:21 PM, <gabriel(dot)ct(at)santamonicace(dot)com(dot)br> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8255
> Logged by: gabriel
> Email address: gabriel(dot)ct(at)santamonicace(dot)com(dot)br
> PostgreSQL version: 8.4.4
You are missing many minor releases. The latest version of 8.4 is
8.4.17. It will also fall in EOL last year, so think about an upgrade!

> Operating system: windows xp
> Description:
>
> Good afternoon, I live in Brazil and I need to create a database with
> encoding LATIN1. how can I make this database. I use windows xp and
> postgreSQL. please send a tutorial on how to makeThank you.
initdb has an option called --encoding allowing to override the
encoding of the template database when initializing server. You can
also specify an encoding with CREATE DATABASE, but use template0 as
template database in this case.
postgres=# create database foo encoding 'LATIN1' TEMPLATE template0;
CREATE DATABASE

For reference:
http://www.postgresql.org/docs/8.4/static/app-initdb.html
http://www.postgresql.org/docs/9.3/static/sql-createdatabase.html
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message varunkarkala 2013-06-27 09:14:35 BUG #8258: I am not able to search composite types in search object
Previous Message Andres Freund 2013-06-27 08:01:35 Re: BUG #8257: Multi-Core Restore fails when containing index comments