From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | mirko(dot)kaffka(at)interface-business(dot)de |
Cc: | pgsql-general(at)postgreSQL(dot)org, PostgreSQL Hackers <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] backend dies suddenly after a lot of error messages |
Date: | 1999-05-12 15:13:10 |
Message-ID: | 25037.926521990@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Mirko Kaffka <mirko(at)interface-business(dot)de> writes:
> We have problems with backend processes that close the channel because of
> palloc() failures. When an INSERT statement fails, the backend reports an
> error (e.g. `Cannot insert a duplicate key into a unique index') and
> allocates a few bytes more memory. The next SQL statement that fails
> causes the backend to allocate more memory again, etc. until we have no
> more virtual memory left. Is this a bug?
Yeah, I'd say so --- all the memory used should get freed at transaction
end, but evidently it isn't happening.
> We are using postgres 6.4.2 on FreeBSD 2.2.8.
I still see it with 6.5-current sources. Will take a look.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ari Halberstadt | 1999-05-12 16:08:02 | crashes on restart with "Tell bgahl@kd6kmx to fix this someday." |
Previous Message | Thomas Reinke | 1999-05-12 11:28:17 | Re: [GENERAL] backend dies suddenly after a lot of error messages |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-05-12 15:16:11 | Re: [HACKERS] More on GROUP BY |
Previous Message | Jan Wieck | 1999-05-12 15:06:09 | Re: [HACKERS] Re: [SQL] plpgsql error |