Skip site navigation (1) Skip section navigation (2)

Re: Performance Improvement by reducing WAL for Update Operation

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
Cc: simon(at)2ndquadrant(dot)com, 'Alvaro Herrera' <alvherre(at)2ndquadrant(dot)com>, noah(at)leadboat(dot)com, horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Performance Improvement by reducing WAL for Update Operation
Date: 2013-01-29 10:22:43
Message-ID: 5107A2F3.5080605@vmware.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 29.01.2013 11:58, Amit Kapila wrote:
> Can there be another way with which current patch code can be made better,
> so that we don't need to change the encoding approach, as I am having
> feeling that this might not be performance wise equally good.

The point is that I don't want to heap_delta_encode() to know the 
internals of pglz compression. You could probably make my patch more 
like yours in behavior by also passing an array of offsets in the new 
tuple to check, and only checking for matches as those offsets.

- Heikki


In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2013-01-29 11:22:15
Subject: Re: [sepgsql 2/3] Add db_schema:search permission checks
Previous:From: Magnus HaganderDate: 2013-01-29 10:15:41
Subject: Re: pg_basebackup with -R option and start standby have problems with escaped password

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group