Message-ID: <4FD7FCFD.6010900@ringerc.id.au>
Date: Wed, 13 Jun 2012 10:37:49 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: Re: Partitioned Tables
References: <20120613000545.GM19474@slacker.ja10629.home>
In-Reply-To: <20120613000545.GM19474@slacker.ja10629.home>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 06/13/2012 08:05 AM, Wayne Cuddy wrote:
> I'm using partitioned tables where a child table is chosen based on a
> time stamp. One child table exists for each month.
>
> I move records from a temp table to the partitioned table via something like
> this:
>
> INSERT INTO parent_table SELECT * FROM temp_table;
>
> All works well but with when inserting to standard tables the insert
> result contains the number of records inserted. I've found that when I
> insert into partitioned tables the result is always zero.

Are you inserting directly into the partition? Or into the parent table?

If you're inserting into the parent, then it's true that no rows were 
inserted into the parent; a trigger redirected the write into the child 
table. Pg's handling of partitioning isn't yet sophisticated enough to 
recognise that those rows got written to a child and thus still appeared 
in the parent and report that.

As a workaround, ignore the insert count for partitioned tables, or 
insert directly into the appropriate partition(s).

--
Craig Ringer