On Thu, Mar 2, 2017 at 11:29 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > After thinking about that for awhile, it seemed like the most useful thing > to do is to set up an errcontext callback that will be active throughout > execution of the start_proc. That will cover both setup failures like > the above, and errors occurring within the start_proc, which could be > equally confusing if you think they apply to the function you initially > tried to call. v2 patch attached that does it like that.
+1 for that approach. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers