On 14 October 2015 at 04:01, Robert Haas <robertmh...@gmail.com> wrote: > This patch is marked as Ready for Committer in the CommitFest > application. Here is my attempt to summarize the votes upthread: > > Tom Lane: plpgsql RAISE is sufficient; we don't need this. > Pavel Stehule: could be replaced by custom function, but not against it. > Robert Haas: plpgsql RAISE is sufficient; we don't need this. > Jim Nasby: A generic wrapper around RAISE is not trivial, so +1. > Andres Freund: I've written this function many times, so let's have it in > core. > David Fetter: I've written this function like 20 times, we should have it.
Not a committer, so I don't really get a vote here, but I think it's useful and I've written a "RAISE" wrapper in plpgsql enough times to think it's useful. I've used it for tracing progress of queries, for aborting queries on error conditions, all sorts of things. -1 for any attempt to bypass log_min_messages etc. If we were going to go there we should do it with proper heirachical logging control, not a special case half measure. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
