On 29 January 2013 16:51, Simon Riggs <[email protected]> wrote: > On 29 January 2013 16:38, Fujii Masao <[email protected]> wrote: > >> On second thought, we don't need such a complicated test case to produce >> the problem which derives from the same cause of reported problem. The >> procedure to produce the problem is: >> >> 1. Set up one master (A) and one standby (B) >> 2. Promote (B) with fast mode after running pgbench -i -s 10 >> 3. Execute the write transaction on new master (B) >> 4. Shut down (B) with immediate mode before end-of-recovery checkpoint >> has been completed >> 5. Restart (B) >> >> Then you can confirm that the write transaction that you executed in #3 has >> been lost. > > Thanks for the test case, that was quick!
OK, I can confirm this bug. This needs more work as is, so I'll revert and re-post. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
