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

Поиск
Список
Период
Сортировка
От Brodie Thiesfield
Тема BUG #3520: insert causing error "invalid memory alloc request size 2147483648"
Дата
Msg-id 200708070341.l773f7WS038481@wwwmaster.postgresql.org
обсуждение исходный текст
Ответы Re: BUG #3520: insert causing error "invalid memory alloc request size 2147483648"  (Gregory Stark <stark@enterprisedb.com>)
Re: BUG #3520: insert causing error "invalid memory alloc request size 2147483648"  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-bugs
The following bug has been logged online:

Bug reference:      3520
Logged by:          Brodie Thiesfield
Email address:      brofield2@jellycan.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

STEPS TO REPRODUCE

See attached file postgre-bug.sql
Execute with "psql dbname < postgre.bug"

Note that this testcase has been reduced as much as appears possible.
Changes to the script will cause the error to go away (e.g. reducing the
number of strings, removing the analyse statements). The error will also
disappear if the data is dumped/loaded with pg_dump and the INSERT statement
executed.

OUTPUT

(at time of final INSERT)
ERROR:  XX000: invalid memory alloc request size 2147483648
LOCATION:  MemoryContextAlloc, mcxt.c:504

See attached file postgre-bug.out

OUTPUT EXPECTED

No error (same SQL works fine in sqlite and MS SQL).

INSTALLATION

>psql --version
psql (PostgreSQL) 8.2.4

Upgrade installation from 8.2.2 using installer, default options.
Error also existed in version 8.2.2
Running on Windows XP SP2 (Japanese)

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Peter Koczan"
Дата:
Сообщение: Re: BUG #3504: Some listening sessions never return from writing, problems ensue
Следующее
От: Gregory Stark
Дата:
Сообщение: Re: RE : RE : BUG #3519: Postgres takes the wrong query plan resulting in performance issues