| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autonomous transactions |
| Date: | 2016-09-03 00:41:31 |
| Message-ID: | 26e133d8-1fc2-0870-1da0-15b2ec71f49a@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/2/16 3:45 AM, Robert Haas wrote:
> So my suggestion is
> that you pursue the work but change the name.
That might make the plpgsql issues significantly easier to deal with as
well, by making it very explicit that you're doing something with a
completely separate connection. That would make requiring special
handling for passing plpgsql variables to a query much less confusing.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2016-09-03 01:02:50 | Re: Issue with bgworker, SPI and pgstat_report_stat |
| Previous Message | Tomas Vondra | 2016-09-03 00:21:17 | Re: pg_dump / copy bugs with "big lines" ? |