From: Greg Stark <gsstark@mit.edu>
To: Ioannis Theoharis <theohari@ics.forth.gr>
Cc: Greg Stark <gsstark@mit.edu>
Cc: ken <southerland@samsixedd.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: inheritance performance
Date: 21 Jan 2005 23:22:13 -0500
Message-ID: <87pszy6qkq.fsf@stark.xeocode.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0501220307100.6097@ourania.ics.forth.gr>
References: <1106295545.6622.266.camel@pesky.s6portland>
<87hdlaahez.fsf@stark.xeocode.com>
<Pine.GSO.4.58.0501220307100.6097@ourania.ics.forth.gr>
Ioannis Theoharis <theohari@ics.forth.gr> writes:
> Can you explain me in more details what kind of optimization is missing in
> that case?
Uh, no I can't really. It was mentioned on the mailing list with regards to
UNION ALL specifically. I think it applied to inherited tables as well but I
wouldn't know for sure. You could search the mailing list archives for recent
discussions of partitioned tables.
In any acse it was a purely technical detail. Some step in the processing of
the data that could be skipped if there weren't any actual changes to the data
being done or something like that. It made a small but noticeable difference
in the runtime but nothing that made the technique infeasible.
--
greg
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-performance@postgresql.org
Cc: gsstark@mit.edu, theohari@ics.forth.gr, southerland@samsixedd.com
Subject: Re: inheritance performance
In-Reply-To: <87pszy6qkq.fsf@stark.xeocode.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