Re: free(): invalid pointer , when to dumping data to a new server

From: "Andres Freund" <andres(at)anarazel(dot)de>
To: "Magnus Hagander" <magnus(at)hagander(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Lars Aksel Opsahl" <Lars(dot)Opsahl(at)nibio(dot)no>, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, "Laurenz Albe" <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: free(): invalid pointer , when to dumping data to a new server
Date: 2020-11-02 23:56:02
Message-ID: d306370e-0584-4778-90f4-562514eb2b42@www.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi,

> FYI, looking at this one in a bit more details it looks like it's
> standard C++ destructors -- they're added to the list of exit handlers
> automatically when C++ is used, AIUI.
>
> Still leaves the problem with postgis/proj of course, but as a
> noteworthy detail. It's not as easy as an explicit atexit().

Yes, there has to be a bug leading to the memory already having been freed or such.

Probably worth trying to run this under valgrind or such.

Andres

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Keith 2020-11-03 05:12:27 Re: Maybe a possible bug in the partitioning code?
Previous Message Holger Jakobs 2020-11-02 21:34:25 Re: pgadmin4 - which python