Re: proposal: PL/Pythonu - function ereport

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Catalin Iacob <iacobcatalin(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(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-08 18:59:08
Message-ID: 20160208185908.GA249894@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I don't think we need to preserve absolutely all the existing behavior
to the letter. We do need to preserve the behavior for sensible cases
that people might be reasonably be using currently; and if there's
anything somewhat obscure but really useful that you currently get by
using some clever trick, them we should provide some reasonable way to
get that functionality with the new stuff too. But this doesn't mean
all existing code must continue to behave in exactly the same way.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2016-02-08 19:00:29 Re: a raft of parallelism-related bug fixes
Previous Message Fabien COELHO 2016-02-08 18:52:30 Re: checkpointer continuous flushing - V16