From: Petr Jelinek <petr@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
To: hlinnaka@iki.fi, Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Sawada Masahiko <sawada.mshk@gmail.com>
Cc: Greg Stark <stark@mit.edu>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Jeff Janes <jeff.janes@gmail.com>
Subject: Re: Reducing tuple overhead
Date: Thu, 23 Apr 2015 18:45:37 +0200
Message-ID: <553921B1.7080204@2ndquadrant.com> (raw)
In-Reply-To: <20150423162429.GG3055@alap3.anarazel.de>
References: <20150423162429.GG3055@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 23/04/15 18:24, Andres Freund wrote:
> Whether that's feasible complexity wise is debatable, but it's certainly
> possible.
>
>
> I do wonder what, in realistic cases, is actually the bigger contributor
> to the overhead. The tuple header or the padding we liberally add in
> many cases...
>
The logical ordering patch + auto optimizations of column layout on
table creation/rewrite might help partially there.
But what seems to be clear is that we need more in depth analysis of
what really contributes most to the tuple size in various use-cases and
then we can debate what we can do about it.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: petr@2ndquadrant.com, andres@anarazel.de, Jim.Nasby@BlueTreble.com, robertmhaas@gmail.com, bruce@momjian.us, sawada.mshk@gmail.com, stark@mit.edu, jeff.janes@gmail.com
Subject: Re: Reducing tuple overhead
In-Reply-To: <553921B1.7080204@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox