Postgres Pro
Downloads
Home   >   mailing lists

Re: Partitioning and ORM tools - Mailing list pgsql-general

From Melvin Davidson
Subject Re: Partitioning and ORM tools
Date
Msg-id CANu8FiyJBGbZFSpGWKnrN1hG8m9Ac4syivm77j_AGG_9fXzQ0g@mail.gmail.com
Whole thread Raw
In response to Partitioning and ORM tools  (CS DBA <cs_dba@consistentstate.com>)
Responses Re: Partitioning and ORM tools  (Rob Sargent <robjsargent@gmail.com>)
Re: Partitioning and ORM tools  (Kris Deugau <kdeugau@vianet.ca>)
List pgsql-general
Tree view
Your problem seems strange as it has never been previously reported for anyone else that has _successfully_ set up partioning.
Perhaps is you provide just a little bit more detail we might be able to help you.
Useful and needed information would be:
1. Version of PostgreSQL
2. Operating System
3. Table structure for partitioned table
4. Trigger function and trigger used for insert
5. The actual insert statement.

On Tue, Mar 22, 2016 at 2:40 PM, CS DBA <cs_dba@consistentstate.com> wrote:
Hi All;

we setup partitioning for a large table but had to back off because the return status (i.e: "INSERT 0 1") returns "INSERT 0 0" when inserting into the partitioned table which causes the ORM tool to assume the insert inserted 0 rows.  Is there a standard / best practices work around for this?

Thanks in advance




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



--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: CS DBA
Date:
Subject: Partitioning and ORM tools
Next
From: Rob Sargent
Date:
Subject: Re: Partitioning and ORM tools