Re: pg_upgrade segfault (was: pg_migrator segfault) - Mailing list pgsql-general

From hernan gonzalez
Subject Re: pg_upgrade segfault (was: pg_migrator segfault)
Date
Msg-id AANLkTikRXCDDi_GRDU9Czsc+UYyw1wGB=NAVtNbPqiRD@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade segfault (was: pg_migrator segfault)  (hernan gonzalez <hgonzalez@gmail.com>)
List 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/

pgsql-general by date:

Previous
From: hernan gonzalez
Date:
Subject: Re: pg_upgrade segfault (was: pg_migrator segfault)
Next
From: Tom Lane
Date:
Subject: Re: pg_upgrade segfault (was: pg_migrator segfault)