| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | RUM and WAL-generation |
| Date: | 2020-10-21 08:04:13 |
| Message-ID: | VisenaEmail.3c.31ebd9cf1d8c010d.1754a2b310a@tc7-visena |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi all.
The RUM-index is very nice, but indexes get very large and produce insane
amounts of WAL.
Due to the way PG works (IIUC), updating an int-column in a row produces lots
of WAL because the whole row is duplicated, and if that row holds RUM-indexed
columns it gets really bad...
We hav actually run out of WAL-space in production because of this.
I see this TODO-entry in RUM:
* Improve GENERIC WAL to support shift (PostgreSQL core changes).
What is the status on this?
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias Apitz | 2020-10-21 11:54:01 | using psql 11.4 with a server 13.0 && meta commands |
| Previous Message | John the Scott | 2020-10-21 06:55:22 | Re: rum index supported on pg13? |