| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Incomplete freezing when truncating a relation during vacuum |
| Date: | 2013-12-01 20:54:41 |
| Message-ID: | 5226.1385931281@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> schrieb:
>> Uh ... what does the last have to do with it? Surely we don't run
>> VACUUM on replicas. Or are you talking about what might happen when
>> VACUUM is run on a former replica that's been promoted to master?
> Unfortunately not. The problem is that xl_heap_freeze's redo function simply reexecutes heap-freeze-tuple() instead of logging much about each tuple...
That was a pretty stupid choice ... we should think seriously about
changing that for 9.4. In general the application of a WAL record
needs to be 100% deterministic.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-12-01 22:15:31 | Re: Incomplete freezing when truncating a relation during vacuum |
| Previous Message | Andres Freund | 2013-12-01 20:41:14 | Re: Incomplete freezing when truncating a relation during vacuum |