| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Alexey Kondratov <kondratov(dot)aleksey(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru>, Robert Haas <robertmhaas(at)gmail(dot)com>, Nicolas Barbier <nicolas(dot)barbier(at)gmail(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Anastasia Lubennikova <lubennikovaAV(at)gmail(dot)com> |
| Subject: | Re: [HACKERS] GSOC'17 project introduction: Parallel COPY execution with errors handling |
| Date: | 2018-03-03 14:02:23 |
| Message-ID: | 53988e1e-ce41-f3ca-f6af-c9e43428c0d3@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/3/18 00:48, Tom Lane wrote:
> I don't think that can possibly work. It would only be safe if, between
> the thrower and the catcher, there were no other levels of control
> operating according to the normal error-handling rules. But input
> functions certainly cannot assume that they are only called by COPY,
> so how could they safely throw a "soft error"?
That assumes that throwing a soft error in a context that does not
handle it specially is not safe. I'd imagine in such situations the
soft error just behaves like a normal exception.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-03-03 14:12:27 | Re: Rewriting the test of pg_upgrade as a TAP test - take two |
| Previous Message | Peter Eisentraut | 2018-03-03 13:58:18 | Re: Disabling src/test/[ssl|ldap] when not building with SSL/LDAP support |