| From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Antonis Antoniou <a(dot)antoniou(at)albourne(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: AllocSetAlloc() |
| Date: | 2001-02-21 18:01:05 |
| Message-ID: | Pine.LNX.3.96.1010221185810.12548B-100000@ara.zf.jcu.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 21 Feb 2001, Tom Lane wrote:
> Antonis Antoniou <a(dot)antoniou(at)albourne(dot)com> writes:
> > I would like to know what is causing this error. The machine has 1GB of
> > memory and I use PostgreSQL 7.1beta4.
> > The same function on PostgreSQL 7.0.2 works ok. Could someone explain
> > me what this error means and where to look in order to solve it?
> > select function_name;
> > 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?
Karel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-02-21 18:01:43 | Re: How to release SET() in PgSQL? |
| Previous Message | Tom Lane | 2001-02-21 17:53:49 | Re: AllocSetAlloc() |