Database Research & Development

  • Home
  • NoSQL
    • NoSQL
    • Cassandra
  • Databases
    • Database Theory
    • Database Designing
    • SQL Server Coding Standards
    • SQL Server
    • PostgreSQL
    • MySQL
    • Greenplum
    • Linux
  • Interviews
    • SQL Server Interviews
    • MySQL Interviews
    • SQL Puzzles
  • DBA Scripts
    • SQL Server DBA Scripts
    • PostgreSQL DBA Scripts
    • MySQL DBA Scripts
    • Greenplum DBA Scripts
  • Home
  • Blog Archives !
  • (: Laugh@dbrnd :)
  • Contact Me !
sqlserverinterviews
Home 2015 November PostgreSQL: SELECT Last Inserted ID or Sequence Value

PostgreSQL: SELECT Last Inserted ID or Sequence Value

This article is half-done without your Comment! *** Please share your thoughts via Comment ***

I found that PostgreSQL professionals are wondering about last inserted id or sequence value of PostgreSQL Tables.

You can find an N number of articles and discussion on this point.

Let me clear describe this topic in my words, because this is important for PostgreSQL Database Developers.

The PostgreSQL provideds Sequence object and you can create a Sequence by assigning SERIAL or BIGSERIAL Datatype to the columns.

You can use CURRVAL and LASTVAL to get the last inserted or generated ID by the Sequence object.

These both are concurrently safe, and behaviour of Postgres Sequence is designed such a way that different sessions will not interfere with each other.

But sometimes, I found the wrong ID by CURRVAL or LASTVAL because there is some additional trigger rule written like when you insert one row in X table, some other row also require to insert in Y table using an INSERT Trigger.

When some extra insertion or load of insertion is going on by the different sources, LASTVAL and CURRVAL return the wrong ID. This is the very rare situation, but still, the risk is there.

The best solution is – PostgreSQL INSERT RETURNING:
Using INSERT RETURNING, you can select last inserted id for that only INSERT at the time of insertion.

Below is a small demo:

Create a sample table:

1
2
3
4
5
6
7
CREATE TABLE tbl_TestReturnID
(
Rno SERIAL
,Name CHARACTER VARYING
,Address CHARACTER VARYING
,CONSTRAINT pk_tbl_TestReturnID_Rno PRIMARY KEY(Rno)
);

Insertion with RETURNING a last inserted value:

1
2
INSERT INTO tbl_TestReturnID (Name,Address)
VALUES ('Anvesh','Hyderabad') RETURNING Rno;

After executing above INSERT statement, you will get the last inserted ID.
My Suggestion is to use RETURNING instead of CURRVAL and LASTVAL.

Nov 8, 2015Anvesh Patel
SQL Server: Script to find Missing IndexesSQL Server: Error 701 There is insufficient system memory to run this query
Comments: 2
  1. Felipa
    December 6, 2015 at 6:44 pm

    Thanks in support of sharing such a fastidious thinking, piece of writing
    is fastidious, thats why i hve read it completely

  2. Ashvin
    April 28, 2016 at 12:34 pm

    You are a very capable individual!
    God bless you !

Anvesh Patel
Anvesh Patel

Database Engineer

November 8, 2015 PostgreSQLAnvesh Patel, database, database research and development, dbrnd, insert, plpgsql, Postgres Query, postgresql, PostgreSQL Administrator, PostgreSQL Error, PostgreSQL Programming, PostgreSQL Tips and Tricks, returning, sequence
About Me!

I'm Anvesh Patel, a Database Engineer certified by Oracle and IBM. I'm working as a Database Architect, Database Optimizer, Database Administrator, Database Developer. Providing the best articles and solutions for different problems in the best manner through my blogs is my passion. I have more than six years of experience with various RDBMS products like MSSQL Server, PostgreSQL, MySQL, Greenplum and currently learning and doing research on BIGData and NoSQL technology. -- Hyderabad, India.

About DBRND !

dbrnd

This is a personal blog (www.dbrnd.com).

Any views or opinions represented in this blog are personal and belong solely to the blog owner and do not represent those of people, institutions or organizations that the owner may or may not be associated with in professional or personal capacity, unless explicitly stated.

Feel free to challenge me, disagree with me, or tell me I’m completely nuts in the comments section of each blog entry, but I reserve the right to delete any comment for any reason whatsoever (abusive, profane, rude, or anonymous comments) - so keep it polite.

The content of this website is protected by copyright. No portion of this website may be copied or replicated in any form without the written consent of the website owner.

Recent Comments !
  • Anvesh Patel { Sure will do... } – May 27, 12:43 PM
  • Anvesh Patel { Great... } – May 27, 12:41 PM
  • Anvesh Patel { Great... } – May 27, 12:39 PM
  • Anvesh Patel { Great... } – May 27, 12:36 PM
  • Anvesh Patel { Great... } – May 27, 12:28 PM
  • Anvesh Patel { Great... } – May 27, 12:27 PM
  • Anvesh Patel { Great... } – May 27, 12:16 PM
  • Older »
Follow Me !
  • facebook
  • linkedin
  • twitter
  • youtube
  • google
  • flickr
© 2015 – 2019 All rights reserved. Database Research & Development (dbrnd.com)
Posting....