Skip site navigation (1) Skip section navigation (2)

Re: [Pgbuildfarm-members] [Fwd: RE: Build farm on Windows]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PGBuildFarm <pgbuildfarm-members(at)pgfoundry(dot)org>, Phil Cairns <phil(at)pagaros(dot)com(dot)au>
Subject: Re: [Pgbuildfarm-members] [Fwd: RE: Build farm on Windows]
Date: 2006-07-28 20:39:50
Message-ID: 999.1154119190@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> WARNING:  could not read time zone file
> "/home/pgbuild/devel/pginst/share/postgresql/timezonesets/Default": No
> such file or directory

> so it's there but as a msys-virtual path - is that get passed to some
> win32 function expecting a windows-style path ?

Doh, I see what's the problem: we calculate the sharedir path using
my_exec_path, and falling back to the hardwired PGSHAREDIR path if
my_exec_path isn't correct.  The problem is that in a Windows
subprocess, my_exec_path isn't correct until read_backend_variables
has been done, and *that happens after InitializeGUCOptions* in
SubPostmasterMain().  So we're trying to set up the tz name data
before we have the path we need.

The reason I didn't notice this in testing with EXEC_BACKEND is that
I wasn't testing in a relocated installation, and so the fallback
get_share_path calculation got the right answer anyway.

Not sure about a clean fix.  Probably we'll have to do something
similar to the way TimeZone is handled, where we don't try to read
in the data until later on in the initialization sequence.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Phil FrostDate: 2006-07-28 20:42:11
Subject: Re: lastval exposes information that currval does not
Previous:From: Andrew DunstanDate: 2006-07-28 20:35:14
Subject: Re: [Pgbuildfarm-members] [Fwd: RE: Build farm on Windows]

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group