Re: Performance Improvement by reducing WAL for Update Operation

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com>
Subject: Re: Performance Improvement by reducing WAL for Update Operation
Date: 2014-02-04 22:03:15
Message-ID: CAM3SWZR7VE=oKVpnHp0Pn624zaveQC3Y9wjSmXycKQV=yKiwHA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 4, 2014 at 1:58 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> I think there's zero overlap. They're completely complimentary features. It's not like normal WAL records have an irrelevant volume.

I'd have thought so too, but I would not like to assume. Like many
people commenting on this thread, I don't know very much about
compression.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2014-02-04 22:21:51 Re: integrate pg_upgrade analyze_new_cluster.sh into vacuumdb
Previous Message Josh Berkus 2014-02-04 22:03:12 Re: jsonb and nested hstore