| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Sriram Dandapani" <sdandapani(at)counterpane(dot)com> |
| Cc: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: autovacuum ignore tables |
| Date: | 2006-09-29 21:48:12 |
| Message-ID: | 3959.1159566492@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Sriram Dandapani" <sdandapani(at)counterpane(dot)com> writes:
> The jdbc inserts go into the main parent table and check constraints
> redirect them to child tables.
A check constraint can't redirect anything. Are you saying that you use
a trigger to try to insert the row into *each* child table, relying on
the constraints to make all except one insert fail? Ugh. You'd do a
lot better to duplicate the partitioning-rule knowledge in the trigger,
and do only one insert that should succeed --- no wasted cycles, and no
need for a subtransaction.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sriram Dandapani | 2006-09-29 21:54:24 | Re: autovacuum ignore tables |
| Previous Message | Sriram Dandapani | 2006-09-29 21:44:15 | Re: [JDBC] number of transactions doubling |