Re: BUG #6246: character encoding for 64 bit

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Susannah" <cyclingrelf(at)gmail(dot)com>,<pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6246: character encoding for 64 bit
Date: 2011-10-12 16:19:15
Message-ID: 4E9577B30200002500041EB4@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Susannah <cyclingrelf(at)gmail(dot)com> wrote:

> FATAL: conversion between WIN1252 and LATIN1 is not supported

WIN1512 supports characters which are not supported by LATIN1. If
you sent such characters to the database, what would you expect to
happen?

> I can connect through pgAdmin and create tables etc, just not with
> psql.

Perhaps pgAdmin detects the mismatch and sets the client-side
character set to the more limited LATIN1? What does pgAdmin do if
you make such a connection and then try to store a character which
is not in the LATIN1 character set, like a euro character?

-Kevin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2011-10-12 16:28:06 Re: BUG #6252: After drop the default database 'postgres', I can not create a database by 'createdb.exe'
Previous Message Tom Lane 2011-10-12 15:40:32 Re: [BUGS] *.sql contrib files contain unresolvable MODULE_PATHNAME