Re: Speeding up INSERTs and UPDATEs to partitioned tables

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, kato-sho(at)jp(dot)fujitsu(dot)com
Subject: Re: Speeding up INSERTs and UPDATEs to partitioned tables
Date: 2018-11-16 13:38:58
Message-ID: 20181116133858.63uggshkl3vhqvcf@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

One thing I don't quite like is the inconsistency in handling memory
context switches in the various function allocating stuff. It seems
rather haphazard. I'd rather have a memcxt member in
PartitionTupleRouting, which is set when the struct is created, and then
have all the other functions allocating stuff use that one.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message James Coleman 2018-11-16 14:00:27 Re: Convert MAX_SAOP_ARRAY_SIZE to new guc
Previous Message Tomas Vondra 2018-11-16 13:32:50 Re: wal_dump output on CREATE DATABASE