From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Catalin Iacob <iacobcatalin(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: PL/Pythonu - function ereport |
Date: | 2016-02-13 15:26:30 |
Message-ID: | CAFj8pRAubCjTrHGa6f-Rjw1UvdPVHB0QYSGDWSjO-uLSH4jXpQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
I am sending new version. Current version does:
1. the plpy utility functions can use all ErrorData fields,
2. there are no new functions,
3. via GUC plpythonu.legacy_custom_exception we can return previous behave,
4. only exception Error is raised with natural structure - no composite
value spidata.
5. fields: message, detail and hint are implicitly translated to string -
it decrease a necessity of legacy mode
Curent version doesn't do:
1. touch plpy exception classes.
A doc should be enhanced, but the code should be +/- final.
Regards
Pavel
Attachment | Content-Type | Size |
---|---|---|
plpython-enhanced-error-01.patch | text/x-patch | 30.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-02-13 15:28:54 | Re: pg_basebackup vs WAL fetching |
Previous Message | Craig Ringer | 2016-02-13 15:25:06 | Re: pg_basebackup vs WAL fetching |