Re: Partitioning and ORM tools

From: Kris Deugau <kdeugau(at)vianet(dot)ca>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Partitioning and ORM tools
Date: 2016-03-22 19:58:30
Message-ID: 56F1A3E6.6040709@vianet.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Melvin Davidson wrote:
> Your problem seems strange as it has never been previously reported for
> anyone else that has _successfully_ set up partioning.

At least as of when I asked a very similar question
(http://www.postgresql.org/message-id/flat/547F7E88(dot)7080901(at)vianet(dot)ca#547F7E88(dot)7080901@vianet.ca),
the answer amounted to "deal with it", "don't use partitioning",
"copy-and-delete rather than redirecting the INSERT" (causes undesirable
VACUUM side effects) or "insert directly in the child table".

The problem is not data going astray, or not getting inserted at all,
it's the fact that the number of rows inserted is returned as 0 - due to
the fact that the rows are not in fact inserted in the parent table when
configured as per the example in the docs.

-kgd

In response to

Browse pgsql-general by date

  From Date Subject
Next Message CS DBA 2016-03-22 20:09:27 Re: Partitioning and ORM tools
Previous Message Rob Sargent 2016-03-22 19:10:09 Re: Partitioning and ORM tools