Re: BUG #3520: insert causing error "invalid memory alloc request size 2147483648"

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Brodie Thiesfield <brofield2(at)jellycan(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3520: insert causing error "invalid memory alloc request size 2147483648"
Date: 2007-08-07 18:32:38
Message-ID: 46B8BAC6.7030706@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Brodie Thiesfield wrote:
> The database is created in UTF-8.
> CREATE DATABASE crossbase WITH OWNER = tserver ENCODING = 'UTF-8';
>
> postgres=# \l
> 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.

It certainly looks like that bug. Any chance you're experienced enough
to set a breakpoint at it and get a backtrace when the error shows up?
(I know it's very difficult on windows with the current version). Or if
you can try the tip of the REL8_2_STABLE branch in cvs?

//Magnus

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Decibel! 2007-08-07 22:06:04 Re: BUG #3514: buggy install + no manual support (add)
Previous Message Mouhamadou Dia 2007-08-07 14:31:14 RE : RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues