Re: pg_upgrade segfault (was: pg_migrator segfault)

From: hernan gonzalez <hgonzalez(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_upgrade segfault (was: pg_migrator segfault)
Date: 2010-11-02 19:07:44
Message-ID: AANLkTikRXCDDi_GRDU9Czsc+UYyw1wGB=NAVtNbPqiRD@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Replacing that 1 for 2 it's enough for making it work, for me, it seems.

But it's not enough to get valgrind happy (It still reports 4 "definitely
lost" blocks, all from that putenv2 function). Perhaps that's related to the
comment:

/*
* Do not free envstr because it becomes part of the environment
* on some operating systems. See port/unsetenv.c::unsetenv.
*/

Hernán J. González
http://hjg.com.ar/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-11-02 19:23:37 Re: pg_upgrade segfault (was: pg_migrator segfault)
Previous Message hernan gonzalez 2010-11-02 19:00:29 Re: pg_upgrade segfault (was: pg_migrator segfault)