Re: Hot Standby and prepared transactions

>That fixes or explains all known issues, from me. Are there any other
>things you know about that I haven't responded to? Do you think we have
>addressed every issue, except deferred items?
>
>I will be looking to commit to CVS later today; waiting on any
>objections.
>

Is following problem reported or fixed ?

-----
1. configure with --enable-cassert option, then make, make install
2. initdb, enable WAL archiving
3. run the server
4. run pgbench -i, with scaling factor 10 or more
5. server dies with following backtrace

(gdb) backtrace
#0  0x009e17a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x00a22815 in raise () from /lib/tls/libc.so.6
#2  0x00a24279 in abort () from /lib/tls/libc.so.6
#3  0x082dbf98 in ExceptionalCondition (conditionName=0x84201d4 "!(lock->nGranted == 1)", errorType=0x8308dd4
"FailedAssertion",  fileName=0x8420fb2 "lock.c", lineNumber=2296) at assert.c:57
 
#4  0x08231127 in GetRunningTransactionLocks (nlocks=0x0) at lock.c:2296
#5  0x0822c110 in LogStandbySnapshot (oldestActiveXid=0x0, nextXid=0x0) at standby.c:578
#6  0x080cc13f in CreateCheckPoint (flags=32) at xlog.c:6826
#7  0x08204cf6 in BackgroundWriterMain () at bgwriter.c:490
#8  0x080ec291 in AuxiliaryProcessMain (argc=2, argv=0xbff25cc4) at bootstrap.c:413
#9  0x0820b0af in StartChildProcess (type=Variable "type" is not available.
) at postmaster.c:4218
#10 0x0820c722 in reaper (postgres_signal_arg=17) at postmaster.c:2322
#11 <signal handler called>
#12 0x009e17a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#13 0x00abcbbd in ___newselect_nocancel () from /lib/tls/libc.so.6
#14 0x0820b2b8 in ServerLoop () at postmaster.c:1360
#15 0x0820d59e in PostmasterMain (argc=3, argv=0x8579860) at postmaster.c:1065
#16 0x081b78f8 in main (argc=3, argv=0x8579860) at main.c:188
-----

Also, is the problem reported in http://archives.postgresql.org/pgsql-hackers/2009-12/msg01324.php
fixed or deferred ?


regrards,


-- Hiroyuki YAMADA Kokolink Corporation yamada@kokolink.net