| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE. |
| Date: | 2016-04-27 16:03:38 |
| Message-ID: | 20160427160338.3t5ytdubnku3grjv@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-04-27 11:59:39 -0400, Robert Haas wrote:
> Masahiko Sawada posted a patch that fixes the problem for him, which
> does not involve any new WAL record type. It also seems to be fixing
> the problem in a way that is clean and consistent with what we've done
> elsewhere.
It only fixes one symptom, the relcache entry is still wrong
afterwards. Which is pretty relevant for planning.
> The patch actually under discussion here manages to introduce a new
> WAL record type without fixing that problem.
It does fix the problem, just not in a super robust way. Which is why I
think we should add something like Masahiko's fix additionally.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-04-27 16:08:08 | Re: EXPLAIN VERBOSE with parallel Aggregate |
| Previous Message | Robert Haas | 2016-04-27 16:00:43 | Re: pgindent |