The database is created in UTF-8.
CREATE DATABASE crossbase WITH OWNER = tserver ENCODING = 'UTF-8';
List of databases
Name | Owner | Encoding
crossbase | tserver | UTF8
crosstest | postgres | UTF8
postgres | postgres | UTF8
template0 | postgres | UTF8
template1 | postgres | UTF8
System locale is Japanese cp932.
lc_collate | Japanese_Japan.932
lc_ctype | Japanese_Japan.932
lc_messages | Japanese_Japan.932
lc_monetary | Japanese_Japan.932
lc_numeric | Japanese_Japan.932
lc_time | Japanese_Japan.932
If there are any other settings you need from show all then it is in
the attached file.
On 8/7/07, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Tue, Aug 07, 2007 at 03:41:07AM +0000, Brodie Thiesfield wrote:
> > The following bug has been logged online:
> > Bug reference: 3520
> > Logged by: Brodie Thiesfield
> > Email address: brofield2(at)jellycan(dot)com
> > PostgreSQL version: 8.2.4
> > Operating system: Windows XP SP2
> > Description: insert causing error "invalid memory alloc request size
> > 2147483648"
> > Details:
> > See SQL script and output at:
> > http://jellycan.com/etc/postgres-bug.zip
> This looks like it could be this bug:
> I've been unable to reproduce it on CVS HEAD, which could be why.
> What encoding is your database in? Is it also UTF-8?
Description: text/plain (24.8 KB)
In response to
pgsql-bugs by date
|Next:||From: Mouhamadou Dia||Date: 2007-08-07 14:31:14|
|Subject: RE : RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues |
|Previous:||From: Mouhamadou Dia||Date: 2007-08-07 14:27:55|
|Subject: RE : RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues|