Tom Lane wrote:
> I wrote:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>> The TimeZone changes are looking might suspicious ...
>
>> FATAL: failed to initialize timezone_abbreviations to "Default"
>
>> Hm. It looks like this is working in the postmaster but failing
>> in subprocesses. I'll see if I can duplicate it using EXEC_BACKEND.
>
> Nope, works fine with EXEC_BACKEND, so it's something Windows-specific.
> I'm not sure why you're not getting any more specific messages ---
> they should be coming out at WARNING level AFAICS. You'll need to trace
> through load_tzoffsets() and see why it's failing in the subprocess.
that was a bit painful but we failed to see a useful error message due
to the fact that we have been activly suppressing it - with a quick hack
like:
---
/home/pgbuild/pgfarmbuild/HEAD/pgsql/src/backend/utils/misc/tzparser.c Tue Jul 25 05:51:21 2006
+++ src/backend/utils/misc/tzparser.c Fri Jul 28 19:33:24 2006
@@ -326,7 +326,6 @@ if (!tzFile) { /* at level 0, if file doesn't exist, guc.c's complaint
is enough */
- if (errno != ENOENT || depth > 0) ereport(tz_elevel,
(errcode_for_file_access(), errmsg("could not read time
zone file \"%s\": %m",
(will probably get mangled by my mailer)
I get a much more useful:
WARNING: could not read time zone file "Default": No such file or directory
FATAL: failed to initialize timezone_abbreviations to "Default"
WARNING: could not read time zone file "Default": No such file or directory
FATAL: failed to initialize timezone_abbreviations to "Default"
LOG: background writer process (PID 3776) exited with exit code 0
LOG: terminating any other active server processes
WARNING: could not read time zone file "Default": No such file or directory
FATAL: failed to initialize timezone_abbreviations to "Default"
LOG: all server processes terminated; reinitializing
WARNING: could not read time zone file "Default": No such file or directory
which gives a strong further hint at the underlying issue.
Stefan
