| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] WAL logging problem in 9.4.3? |
| Date: | 2018-07-25 14:08:33 |
| Message-ID: | 20180725140833.GC6660@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 18, 2018 at 05:58:16PM +0300, Heikki Linnakangas wrote:
> I'd suggest that we continue based on the patch that Kyotaro posted at
> https://www.postgresql.org/message-id/20180330.100646.86008470.horiguchi.kyotaro%40lab.ntt.co.jp.
Whatever happens here, perhaps one way to move on would be to commit
first the TAP test that I proposed upthread. That would not work for
wal_level=minimal so this part should be commented out, but that's
easier this way to test basically all the cases we talked about with any
approach taken.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2018-07-25 14:12:29 | Re: Explain buffers wrong counter with parallel plans |
| Previous Message | Arcadiy Ivanov | 2018-07-25 13:58:31 | Optimizer misses big in 10.4 with BRIN index |