| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vacuum/visibility is busted |
| Date: | 2013-02-08 04:38:18 |
| Message-ID: | 20130208043818.GF5172@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera escribió:
> Alvaro Herrera escribió:
>
> > Hm, if the foreign key patch is to blame, this sounds like these tuples
> > had a different set of XMAX hint bits and a different Xmax, and they
> > were clobbered by something like vacuum or page pruning.
>
> Hm, I think heap_freeze_tuple is busted, yes.
This patch seems to fix the problem for me. Please confirm.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| fix-freeze.patch | text/x-diff | 1020 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Dunstan | 2013-02-08 04:39:35 | Re: [JDBC] JPA + enum == Exception |
| Previous Message | Tom Lane | 2013-02-08 04:07:00 | Re: issues with range types, btree_gist and constraints |