Re: Double Free or corruption
| От | Amol Bhangdiya |
|---|---|
| Тема | Re: Double Free or corruption |
| Дата | |
| Msg-id | CADaB4eA7JuANMTox6zkjv_i4GWFPQDF27+RzJ=5yRfYR8JX7dA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Double Free or corruption (Payal Singh <payal@omniti.com>) |
| Ответы |
Re: Double Free or corruption
|
| Список | pgsql-novice |
Hi Ishaya,
Are you using palloc and pfree for memory management?
If not then it should be the correct way to allocate memory in postgreSQL
Regards,
Amol Bhangdiya
Are you using palloc and pfree for memory management?
If not then it should be the correct way to allocate memory in postgreSQL
Regards,
Amol Bhangdiya
On Wed, Oct 30, 2013 at 9:09 PM, Payal Singh <payal@omniti.com> wrote:
Which OS and postgres version are you using?On Wed, Oct 30, 2013 at 5:53 AM, Ishaya Bhatt <ishayabhatt@gmail.com> wrote:I am modifying code of sorting query, but instead of the required output, this error is thrown in the logs.Hi,Does anyone have any idea what is the cause for the below error:
*** glibc detected *** postgres: ishaya mydb [local] SELECT: double free or corruption (!prev): 0x00000000026bc710 ***
В списке pgsql-novice по дате отправления: