| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SET TRANSACTION in PL/pgSQL |
| Date: | 2018-03-29 16:30:08 |
| Message-ID: | 6a02a934-5f1e-d7a8-297a-46865876883e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/15/18 17:49, Alexander Korotkov wrote:
> I didn't dig deeply into this subject. But should we rather teach SPI
> to execute
> utility statements without taking snapshot when not necessary. That seems
> like what executor do for client provided queries. And that seems a bit
> unlogical
> that SPI behaves differently.
Here is the same patch rewritten using SPI, using the new no_snapshots
facility recently introduced.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-PL-pgSQL-Add-support-for-SET-TRANSACTION.patch | text/plain | 11.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2018-03-29 16:34:58 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |
| Previous Message | Simon Riggs | 2018-03-29 16:26:11 | Re: Changing WAL Header to reduce contention during ReserveXLogInsertLocation() |