| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vacuum/visibility is busted |
| Date: | 2013-02-07 08:35:15 |
| Message-ID: | CA+U5nM+Aw_RiDA7mnqUCBHoPfLr04p9__fqbSRntUehwv9eybw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7 February 2013 05:39, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> While stress testing Pavan's 2nd pass vacuum visibility patch, I realized
> that vacuum/visibility was busted. But it wasn't his patch that busted it.
> As far as I can tell, the bad commit was in the range
> 692079e5dcb331..168d3157032879
Please define "busted" so we can all help track this down.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2013-02-07 08:41:39 | Re: [COMMITTERS] pgsql: Fast promote mode skips checkpoint at end of recovery. |
| Previous Message | Michael Paquier | 2013-02-07 08:28:53 | Re: Support for REINDEX CONCURRENTLY |