Re: Post-mortem: final 2PC patch

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-patches(at)postgresql(dot)org, Magnus Hagander <mha(at)sollentuna(dot)net>
Subject: Re: Post-mortem: final 2PC patch
Date: 2005-06-18 17:58:07
Message-ID: 42B460AF.2060106@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>
>>the machine had some issues a week ago or so - but it looks like the
>>problem occured first here:
>
>
> Hmm, what kind of issues, and are you sure they are fixed?

admin error :-).
I had a second postgresql instance running causing the buildfarm runs to
report a failure because of shared memory-limits.
Had nothing to do with hardware problems though ...

>
> The stack trace looks to me like it is trying to apply the PGTZ setting
> that's coming in from the client during startup. Now I could believe a
> platform-specific breakage there from Magnus' recent hacking, but the
> problem is that *every* backend launched during the regression tests
> is going to be doing this, and doing it in the same way with the same
> value. It's pretty tough to see why some backends would fail at this
> spot and some not ... unless what it is is an intermittent hardware
> problem. Is there a version of memtest86 that works on your machine?

memtest86 works on x86 CPU's only afaik - no ?

anyway - here is the promised backtrace:

#0 0x000000004489fba4 in memcpy () from /usr/lib/libc.so.34.2
#1 0x0000000000326f9c in hash_search (hashp=0xa6e030, keyPtr=0xa5ff90,
action=HASH_ENTER, foundPtr=0x0) at dynahash.c:653
#2 0x00000000003434f0 in pg_tzset (name=0xa5ff90 "PST8PDT") at pgtz.c:1039
#3 0x00000000001fbcf0 in assign_timezone (value=0xa5ff90 "PST8PDT",
doit=1 '\001', source=PGC_S_CLIENT) at variable.c:351
#4 0x0000000000330f28 in set_config_option (name=0xa52830 "timezone",
value=0xa52870 "PST8PDT", context=10645504, source=PGC_S_CLIENT,
isLocal=0 '\0',
changeVal=1 '\001') at guc.c:3748
#5 0x000000000029b5f0 in PostgresMain (argc=4, argv=0xa52928,
username=0xa52740 "mastermind") at postgres.c:2759
#6 0x000000000026b180 in BackendRun (port=0xa77800) at postmaster.c:2800
#7 0x000000000026aa30 in BackendStartup (port=0xa77800) at
postmaster.c:2440
#8 0x00000000002685fc in ServerLoop () at postmaster.c:1221
#9 0x0000000000267bc8 in PostmasterMain (argc=0,
argv=0xffffffffffff57d8) at postmaster.c:930
#10 0x0000000000220cc8 in main (argc=6, argv=0xffffffffffff57d8) at
main.c:268

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-06-18 18:08:55 Re: Two-phase commit
Previous Message Tom Lane 2005-06-18 17:25:44 Re: Post-mortem: final 2PC patch

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-06-18 18:08:55 Re: Two-phase commit
Previous Message Tom Lane 2005-06-18 17:25:44 Re: Post-mortem: final 2PC patch