| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bump default wal_level to logical |
| Date: | 2020-06-08 20:20:53 |
| Message-ID: | CAH2-WznVBnRkAa5L-KCEx-p8GUcTHkMh1azFED7s7Rk7v2VUag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 8, 2020 at 12:28 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> On a quantum-mechanics level, sure, but after Andres's snapshot
> scalability patches, will it be measurable? (Besides, if your workload
> is so high that you're measurably affected by the additional unused
> PGPROC entries, you can always tune it lower.)
The point that Robert went on to make about the increased WAL volume
from logging old primary key (or replica identity) values was a
stronger argument, IMV.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2020-06-08 20:41:29 | Re: hashagg slowdown due to spill changes |
| Previous Message | Alvaro Herrera | 2020-06-08 20:15:17 | Re: hashagg slowdown due to spill changes |