Re: Weird PL/Python elog output

From: Marko Kreen <markokr(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Weird PL/Python elog output
Date: 2009-10-31 20:45:29
Message-ID: e51f66da0910311345l214c0ccekd6f74199b9051f10@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/31/09, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On fre, 2009-10-30 at 17:13 +0200, Marko Kreen wrote:
> > I vote for handling tuple with 1 element better, otherwise keep old
> > behaviour.
> >
> > I don't think breaking multi-arg calls is good idea, as they may be used
> > only in special situations. OTOH, it does not seem worthwhile to
> > spend effort trying to handle them better.
>
> OK, how about this:

Seems OK by me.

--
marko

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2009-10-31 21:00:38 Re: WIP: push AFTER-trigger execution into ModifyTable node
Previous Message Andrew Dunstan 2009-10-31 19:27:39 Re: Unicode UTF-8 table formatting for psql text output