From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ana Carolina Brito de Almeida" <anacrl(at)ig(dot)com(dot)br> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: stack smashing detected |
Date: | 2008-04-15 15:38:16 |
Message-ID: | 14992.1208273896@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Ana Carolina Brito de Almeida" <anacrl(at)ig(dot)com(dot)br> writes:
> I'm trying test a version extended of Postgresql, but when I run a command
> after 9 times, I receive this message in psql:
> ***stack smashing detected***
> And Log said that postgres terminated with signal 6.
> I increased buffer to 120MB and the linux buffer (shmmax) to 2GB.
> What value can I put to max_connections?
You're thinking in the wrong terms entirely. This is a bug that you
need to find/fix in whatever your extension is. I'd look for things
like overrunning a fixed-size array allocated as a local variable.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2008-04-15 15:41:07 | Re: [SQL] rule for update view that updates/inserts into 2 tables |
Previous Message | Martijn van Oosterhout | 2008-04-15 15:36:48 | Re: pulling libpqtypes from queue |