| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Fast promote mode skips checkpoint at end of recovery. |
| Date: | 2013-01-30 17:26:26 |
| Message-ID: | CA+U5nMJGJkiLH-+GH+NHvrZm=czxQjeRvZn4umODH2sL8kcMZQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 29 January 2013 16:51, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 29 January 2013 16:38, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-01-30 19:18:26 | pgsql: Fix grammar for subscripting or field selection from a sub-SELEC |
| Previous Message | Peter Eisentraut | 2013-01-30 04:01:08 | pgsql: pg_regress: Allow overriding diff options |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-01-30 17:59:52 | Re: sql_drop Event Trigger |
| Previous Message | Dimitri Fontaine | 2013-01-30 17:10:24 | Event Triggers Patch Series |