From: PropAAS DBA <dba@propaas.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Partitioning & ORM apps
Date: Sat, 18 Nov 2017 19:49:26 -0700
Message-ID: <46231efa-8a34-17bf-81d2-3c68e05d3565@propaas.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Hi All;
we want to deploy partitioning for historical data archiving &
performance however the app uses an ORM and depends on the number of
rows affected from the inserts, updates & deletes which of course always
come back as zero rows for the partition base or master table.
We talked about letting daily data go into the base table and 'moving'
it nightly but this could still lead to an update/delete for rown in the
child tables, thus the same issue remains.
Anyone know of a workaround? Maybe it can be done with
insert/update/delete trigger functions?
Thanks in advance
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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-admin@postgresql.org
Cc: dba@propaas.com
Subject: Re: Partitioning & ORM apps
In-Reply-To: <46231efa-8a34-17bf-81d2-3c68e05d3565@propaas.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