Jie Liang wrote:

Does 7.3* support this? Can you tell me a bit more about it, please?=20=20
Hash aggregate..?


-- CONFIDENTIALITY NOTICE --

This message is intended for the sole use of the individual and entity to w=
hom it is addressed, and may contain information that is privileged, confid=
ential and exempt from disclosure under applicable law. If you are not the =
intended addressee, nor authorized to receive for the intended addressee, y=
ou are hereby notified that you may not use, copy, disclose or distribute t=
o anyone the message or any information contained in the message. If you ha=
ve received this message in error, please immediately advise the sender by =
reply email, and delete the message. Thank you.

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

I had a similar problem after upgrade to 7.4.2,
Try:=20
SET enable_hashagg =3D false;
Before you execute that SELECT stmt=20
If you don't want disable it in postgresql.conf

Jie Liang

-----Original Message-----
From: Adi Alurkar [mailto:adi (AT) sf (DOT) net]=20
Sent: Monday, June 07, 2004 5:01 PM
To: pgsql-admin (AT) postgresql (DOT) org; pgsql-bugs (AT) postgresql (DOT) org
Subject: [ADMIN] out of memory error


Greetings,

During testing of our application we ran into a very odd error:

very randomly during the test the postgresql log file showed a "ERROR:=20=
=20
53200: out of memory"
we changed the logging configuration to log statements causing errors=20
and found the error to be caused by a SELECT,

here is the relevant info from postgresql log file :

ERROR: 53200: out of memory
DETAIL: Failed on request of size 188
LOCATION: AllocSetAlloc, aset.c:700

Interestingly the box did not OOM (i.e nothing in /var/log/messages)
running RHAS3 with PG 7.4.2

-bash-2.05b$ id
uid=3D26(postgres) gid=3D26(postgres) groups=3D26(postgres) -bash-2.05b$ ps=
ql
-V psql (PostgreSQL) 7.4.2 contains support for command-line editing
-bash-2.05b$ cat /etc/redhat-release Red Hat Enterprise Linux ES release
3 (Taroon) -bash-2.05b$ ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) 4
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 7168
virtual memory (kbytes, -v) unlimited

This happens randomly, when the failing SELECT was run via psql it=20
executed w/o error.

Any suggestions on how this can be debugged?

-Adi


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org