Re: Bug in tm2timestamp

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in tm2timestamp
Date: 2013-03-04 20:22:27
Message-ID: 16842.1362428547@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Alvaro Herrera wrote:
>> Another point worth considering is that most of this is duplicated by
>> ecpg's libpgtypes.

> Bah, ignore this.

Huh? I think you're quite right that it'd be a good idea to get rid of
the duplicated code, if we could. It's always been the backend's free
reliance on palloc and elog/ereport that's been stopping that. I think
we might now have a realistic solution for palloc, but what about elog?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2013-03-04 20:27:08 Re: Bug in tm2timestamp
Previous Message Jeff Davis 2013-03-04 20:22:24 Re: Enabling Checksums