On tis, 2012-05-01 at 20:13 -0400, Tom Lane wrote: > I don't deny that we probably need to reclassify a few error cases, > and fix some elogs that should be ereports, before this approach would > be really workable. My point is that it's *close*, whereas "let's > invent some new error severities" is not close to reality and will > break all sorts of stuff.
We might hit a road block because some of these sqlstates are defined by the SQL standard. But at least we should try this first, and if it doesn't work make another field that contains the admin/server-level severity instead of the client-side/flow-control severity level. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
