Re: Table Partitioning - Mailing list pgsql-general

From Richard Onorato
Subject Re: Table Partitioning
Date
Msg-id 1369268830.32750.YahooMailNeo@web141003.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: Table Partitioning  (Raghavendra <raghavendra.rao@enterprisedb.com>)
Responses Re: Table Partitioning
List pgsql-general
Raghavendra,

I am doing my inserts via Java JPA statements embedded in my Data Access Layer.  I can share them if you would like to see them.
 
Regards,

Richard

From: Raghavendra <raghavendra.rao@enterprisedb.com>
To: Richard Onorato <richard_onorato@yahoo.com>
Cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Sent: Wednesday, May 22, 2013 2:39 AM
Subject: Re: [GENERAL] Table Partitioning

On Wed, May 22, 2013 at 6:54 AM, Richard Onorato <richard_onorato@yahoo.com> wrote:
Were you able to get it to insert with the bigserial being used on the table?  

Yes.
 
Every time I go to do an insert into one of the inherited tables I am now getting the following exception:
org.hibernate.HibernateException: The database returned no natively generated identity value


Hmm, I guess you are inserting on the parent table not directly into inherited table.
Can you share the INSERT statement.
 
Is auto-increment supported on table partitioning?
 

Yes, BIGSERIAL will create a sequence that will be shared by all child partitions.
Check below example as per your test case, INSERT statement do not have BIGSERIAL column still its auto-increment and populated data in child tables. 

postgres=# insert into mymappingtable(c1,c2,c3,count,createdtime) values (9,20,30,1,now());
INSERT 0 0
postgres=# insert into mymappingtable(c1,c2,c3,count,createdtime) values (7,20,30,1,now());
INSERT 0 0
postgres=# select * from mymappingtablet5;
 id | c1 | c2 | c3 | count |           createdtime
----+----+----+----+-------+----------------------------------
  8 |  9 | 20 | 30 |     1 | 2013-05-18 02:08:33.061548+05:30 

postgres=# select * from mymappingtablet3;
 id | c1 | c2 | c3 | count |           createdtime
----+----+----+----+-------+----------------------------------
  9 |  7 | 20 | 30 |     1 | 2013-05-18 02:12:03.076529+05:30
(1 row)

(Request not to top-post please ... :)  )

---
Regards,
Raghavendra
EnterpriseDB Corporation


pgsql-general by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [PERFORM] Very slow inner join query Unacceptable latency.
Next
From: Richard Onorato
Date:
Subject: Re: Table Partitioning