Re: [HACKERS] An example of bugs for Hot Standby

n check in HoldingBufferPinThatDelaysRecovery(). regards, -- Hiroyuki YAMADA Kokolink Corporation yam...@kokolink.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] alpha3 release schedule?

nk this problem is must-fix for the final release ? regards, -- Hiroyuki YAMADA Kokolink Corporation yam...@kokolink.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] An example of bugs for Hot Standby

es, which has long history of updation, can be table A. -- Hiroyuki YAMADA Kokolink Corporation yam...@kokolink.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] alpha3 release schedule?

lease for them. > I never think it's selfish. But I see. Thanks for your kind reply. regards, -- Hiroyuki YAMADA Kokolink Corporation yam...@kokolink.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] alpha3 release schedule?

>Hiroyuki Yamada writes: >> Well, I want to know whether the problem I refered to >> in http://archives.postgresql.org/pgsql-hackers/2009-12/msg01641.php >> is must-fix or not. > >> This problem is a corollary of the deadlock problem. This is less catstrophi

Re: [HACKERS] alpha3 release schedule?

ry of the deadlock problem. This is less catstrophic but more likely to happen. If you leave this problem, for example, any long-running transactions, holding any cursors in whatever tables, have a possibility of freezing whole recovery work in HotStandby node until the transaction commit. regards, --

Re: [HACKERS] An example of bugs for Hot Standby

ral problem" above ? regards, -- Hiroyuki YAMADA Kokolink Corporation yam...@kokolink.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Hot Standby and prepared transactions

>On Wed, 2009-12-16 at 19:35 +0900, Hiroyuki Yamada wrote: > >> * There is a window beween gathering lock information in >> GetRunningTransactionLocks() >>and writing WAL in LogAccessExclusiveLocks(). >> * In current lock redo algorithm, locks are released wh

Re: [HACKERS] Hot Standby and prepared transactions

>On Wed, 2009-12-16 at 18:08 +0900, Hiroyuki Yamada wrote: >> >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? &

Re: [HACKERS] Hot Standby and prepared transactions

f8 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 yam...@kokolink.net -- Sent via pgsql-hackers mailing list (pgs

[HACKERS] An example of bugs for Hot Standby

p process calls LockBufferForCleanup() for any of the buffers regards, -- Hiroyuki YAMADA Kokolink Corporation yam...@kokolink.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] An example of bugs for Hot Standby

p process calls LockBufferForCleanup() for any of the buffers regards, -- Hiroyuki YAMADA Kokolink Corporation yam...@kokolink.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers