| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Test-cases for deferred constraints in plpgsql_transaction.sql |
| Date: | 2018-07-04 07:46:58 |
| Message-ID: | 1de60355-3f87-a4ce-4505-e2e843558bb1@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02.07.18 17:11, Ashutosh Sharma wrote:
> Firstly, it would test if the ROLLBACK works as expected when used
> with the deferred constraints in plpgsql procedures. Secondly, it
> would test if the COMMIT/ROLLBACK works as expected for deferrable
> constraints which was initially immediate type but, later it got set
> to deferred using SET CONSTRAINTS command. I just raised this point
> because i couldn't find such test anywhere in plpgsl_transaction.sql
> file. Please let me know if i am missing something here. Thanks.
Deferred constraints operate on a level below PL/pgSQL. PL/pgSQL just
calls the internal commit and rollback functions, and those handle the
rest. So I don't think we gain much by testing all the functionality
that is associated with transactions again in each procedural language.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jamison, Kirk | 2018-07-04 07:47:24 | RE: Recovery performance of DROP DATABASE with many tablespaces |
| Previous Message | Peter Eisentraut | 2018-07-04 07:43:06 | Re: Failed assertion due to procedure created with SECURITY DEFINER option |