Re: [GENERAL] pg_upgrade problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: depesz(at)depesz(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] pg_upgrade problem
Date: 2011-09-05 21:26:00
Message-ID: 15262.1315257960@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Odd it is dying in the memory freeing at executor close --- not in the
> ltree code.

Doesn't seem odd. The glibc complaint previously shown already
indicates this is a memory stomp problem.

--enable-cassert might (or might not) provide additional help.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message MirrorX 2011-09-05 21:27:12 Re: warm standby - apply wal archives
Previous Message Tomas Vondra 2011-09-05 21:23:13 Re: Query runs in 335ms; function in 100,239ms : date problem?

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2011-09-05 22:04:33 Re: Review: prepare plans of embedded sql on function start
Previous Message Bruce Momjian 2011-09-05 21:04:32 Re: [GENERAL] pg_upgrade problem