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 2017 December PostgreSQL 10: Trace the Status of Transaction (Commit, In Progress, Rollback, Aborted)

PostgreSQL 10: Trace the Status of Transaction (Commit, In Progress, Rollback, Aborted)

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

PostgreSQL 10 introduced many useful features that we can use in day to day work.

Now, we can trace the status of the running transaction in PostgreSQL 10. If we have transaction IDs of our sessions and suddenly database crashed or shutdown, we can check the status of those transactions.

We can check the status like Committed, In Progress, Rollback or Aborted. This facility will help a lot for taking a necessary decision on crashed transactions.

PostgreSQL 10 introduced two functions:

txid_current() – will return the current transaction id of a session
txid_status() – will return the status of transaction

Please check the below sample:

Create a sample table:

1
2
CREATE TABLE tbl_stud
(Rno INT, Name Character Varying);

Open a transaction, and insert a record:

1
2
3
4
BEGIN TRANSACTION;
 
INSERT INTO tbl_stud
VALUES (1,'Anvesh');

Check the current transaction id:

1
2
3
4
5
SELECT *FROM txid_current();
 
txid_current
------------
587

Check the status of above transaction id:
It is showing “in progress” because I didn’t commit the transaction yet.

1
2
3
4
5
SELECT txid_status(BIGINT '587');
 
txid_status
-----------
in progress

Now, execute the COMMIT:

1
COMMIT TRANSACTION;

Now, check the status again:

1
2
3
4
5
SELECT txid_status(BIGINT '587');
 
txid_status
-----------
committed

You can also return transaction id, with the insert statement: (Using RETURNING)

1
2
3
4
5
SELECT txid_status(BIGINT '587');
 
txid_status
-----------
committed

Dec 10, 2017Anvesh Patel
PostgreSQL 10: Introduced XML Table - to store XML DocumentPostgreSQL 10: Important - Name change from xlog to wal and location to lsn

Leave a Reply Cancel reply

CAPTCHA
Refresh

*

Anvesh Patel
Anvesh Patel

Database Engineer

December 10, 2017 PostgreSQLAnvesh Patel, COMMIT, database, database research and development, dbrnd, DeadLock, plpgsql, Postgres Query, postgresql, PostgreSQL 10, PostgreSQL Administrator, PostgreSQL Error, PostgreSQL Monitoring, PostgreSQL Performance Tuning, PostgreSQL Programming, PostgreSQL Tips and Tricks, ROLLBACK, transaction, txid_current, txid_status
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....