To resolve this issue I had to create a new table with the same structure than the partitioned table with a trigger for insert and update. All the operations the application have to do are directed to this new table.
When a new record is inserted in the new table the trigger insert a new record with the same values into the partitioned table and then delete all records from this new table. In updates operations the trigger redirect the operation to the partitioned table too.
With this _not elegant_ solution our Java application is able to do its job.
On Tue, May 13, 2008 at 11:48 AM, Nikolas Everett <nik9000@gmail.com> wrote: > I figure this subject belongs on the performance mailing list because it is > about partitioning, which is a performance issue. > > I'm working on partitioning some of the tables used by an application that > uses OpenJPA. It turns out that OpenJPA is sensitive to the numbers > returned when you do an insert. So I put together a test and attached it. > My postgres version is 8.3.1 compiled from source. > > My problem is that this: > test=> INSERT INTO ttt (a, b) VALUES ('5-5-08', 'test11212'); > INSERT 0 0 > Time: 21.646 ms > needs to show: > INSERT 0 1 > > or OpenJPA will not accept it. The insert works, but OpenJPA does not > believe it and aborts the current transaction. > > Is it possible to have partitioning and have insert show the right number of > rows inserted? > > Thanks, > > --Nik > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > >
