From: | hstenger(at)adinet(dot)com(dot)uy |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Automatically ROLLBACK after fall in *ABORT STATE* |
Date: | 2000-07-28 13:48:41 |
Message-ID: | 39818F39.1F5ED616@adinet.com.uy |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello dear people,
We all know PostgreSQL inability to handle exceptions. Inside a transaction, any
error will make it fall in *ABORT STATE*, and any further action not being
ROLLBACK, ABORT or COMMIT, will ask for a ROLLBACK, ABORT or COMMIT statement. I
want to know what exact code is executed inside PostgreSQL, when a ROLLBACK
statement is issued. Knowing that, I will modify backend/tcop/postgres.c, to do
the necesary calls to ROLLBACK, inmediately after AbortCurrentTransaction().
This will make PostgreSQL behave at least just like IBM's DB2, which rolls back
automatically after an error.
Regards,
Haroldo.
--
----------------------+------------------------
Haroldo Stenger | hstenger(at)ieee(dot)org
Montevideo, Uruguay. | hstenger(at)adinet(dot)com(dot)uy
----------------------+------------------------
Visit UYLUG Web Site: http://www.linux.org.uy
-----------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2000-07-28 14:30:56 | Security choices... |
Previous Message | hstenger | 2000-07-28 13:47:49 | Automatically ROLLBACK after fall in *ABORT STATE* |