Re: wrong timezone precision using plpythonu trigger

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: maizi <maizi(at)lirmm(dot)fr>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: wrong timezone precision using plpythonu trigger
Date: 2010-10-12 17:27:20
Message-ID: 1286904440.23137.4.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On mån, 2010-10-11 at 00:13 -0400, Tom Lane wrote:
> It looks to me like this used to work and got broken by this patch:
> http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=3ab8b7fa6f9ac2fb04096f8860261dc42d59a570
>
> which lobotomized plpython to not care about passing the right typmod
> to
> I/O functions. This is a regression, and it's particularly annoying
> because the other three standard PLs get this case right. Peter?

Never thought of that, typmods have a tendency to get lost somehow. :-/
Fix looks good; also good to get rid of the useless PLyTypeInfo
argument.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Rodriguez Fernando 2010-10-12 17:31:31 Re: Could not open file pg_xlog/000000010....
Previous Message paulo pillon 2010-10-12 17:21:38 BUG #5708: configuration php.ini