Re: Fix for pg_upgrade's forcing pg_controldata into English - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Fix for pg_upgrade's forcing pg_controldata into English
Date
Msg-id 201009012356.o81Nuj405114@momjian.us
Whole thread Raw
In response to Re: Fix for pg_upgrade's forcing pg_controldata into English  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fix for pg_upgrade's forcing pg_controldata into English  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Tom Lane wrote:
> >> However, that's something for 9.1 and beyond.  Bruce's immediate problem
> >> is what to do in pg_upgrade in 9.0, and there I concur that he should
> >> duplicate what pg_regress is doing.
> 
> > OK, here is a patch that sets all the variables that pg_regress.c sets.
> 
> I certainly hope that pg_regress isn't freeing the strings it passes
> to putenv() ...

pg_regress does not restore these settings (it says with C/English) so
the code is different.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: compiling with RELCACHE_FORCE_RELEASE doesn't pass regression
Next
From: Tom Lane
Date:
Subject: Re: Fix for pg_upgrade's forcing pg_controldata into English