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
