From: | Ishaya Bhatt <ishayabhatt(at)gmail(dot)com> |
---|---|
To: | Amol Bhangdiya <amol(dot)b89(at)gmail(dot)com> |
Cc: | Payal Singh <payal(at)omniti(dot)com>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Double Free or corruption |
Date: | 2013-10-31 13:24:14 |
Message-ID: | CA+E1M302jUf2rRCTSKn6GD+=0_UrWDMAZrwOReEOG5CJ-yci-g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
I am using Ubuntu 12.04 and PostGreSQL 9.2.4.
On Thu, Oct 31, 2013 at 12:18 AM, Amol Bhangdiya <amol(dot)b89(at)gmail(dot)com> wrote:
> 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
>
>
> On Wed, Oct 30, 2013 at 9:09 PM, Payal Singh <payal(at)omniti(dot)com> wrote:
>
>> Which OS and postgres version are you using?
>>
>> Payal Singh,
>> OmniTi Computer Consulting Inc.
>> Junior Database Architect,
>> Phone: 240.646.0770 x 253
>>
>>
>> On Wed, Oct 30, 2013 at 5:53 AM, Ishaya Bhatt <ishayabhatt(at)gmail(dot)com>wrote:
>>
>>> 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 ***
>>>
>>> I am modifying code of sorting query, but instead of the required
>>> output, this error is thrown in the logs.
>>>
>>
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2013-11-04 14:25:44 | Re: Double Free or corruption |
Previous Message | James David Smith | 2013-10-30 23:48:49 | Re: Import from CSV error |