Message-ID: <50EF0E81.1010808@vmware.com>
Date: Thu, 10 Jan 2013 20:54:57 +0200
From: Heikki Linnakangas <hlinnakangas@vmware.com>
Organization: VMware
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Matheus de Oliveira <matioli.matheus@gmail.com>
CC: pgsql-performance <pgsql-performance@postgresql.org>,
	Charles Gomes <charlesrg@outlook.com>
Subject: Re: Partition insert trigger using C language
References: 
 <CAJghg4KJToKVdr=uecKyOYUjx5h3iNdxYPyhLst=8Lv78Oac+w@mail.gmail.com>
In-Reply-To: 
 <CAJghg4KJToKVdr=uecKyOYUjx5h3iNdxYPyhLst=8Lv78Oac+w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 10.01.2013 20:45, Matheus de Oliveira wrote:
> Inspired by Charles' thread and the work of Emmanuel [1], I have made some
> experiments trying to create a trigger to make partitioning using C
> language.
>
> The first attempt was not good, I tried to use SPI [2] to create a query to
> insert into the correct child table, but it took almost no improvement
> compared with the PL/pgSQL code.

The right way to do this with SPI is to prepare each insert-statement on 
first invocation (SPI_prepare + SPI_keepplan), and reuse the plan after 
that (SPI_execute_with_args).

If you construct and plan the query on every invocation, it's not 
surprising that it's no different from PL/pgSQL performance.

- Heikki


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance