| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
| Cc: | Antonis Antoniou <a(dot)antoniou(at)albourne(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: AllocSetAlloc() |
| Date: | 2001-02-21 18:16:39 |
| Message-ID: | 10996.982779399@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> writes:
> On Wed, 21 Feb 2001, Tom Lane wrote:
> ERROR: Memory exhausted in AllocSetAlloc()
>>
>> If it worked in 7.0 and fails now, then that probably means we have a
>> bug to fix. May we see a complete, reproducible example?
>>
> This error returns aset.c only if malloc() ruturs NULL. Not is a proble in
> OS/libs?
Not necessarily. Certainly aset.c thinks it's run out of memory, but why?
It could be some bit of our code computing a ridiculous request size,
for example, or a serious memory leak under the right conditions.
That's why I want to see Antonis' example.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Szabolcs Borbely | 2001-02-21 18:29:20 | PostgreSQL 7 on Solaris 8 - Is it working? |
| Previous Message | Tom Lane | 2001-02-21 18:01:43 | Re: How to release SET() in PgSQL? |