Re: Tightening binary receive functions

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: James William Pye <lists(at)jwp(dot)name>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Tightening binary receive functions
Date: 2010-02-18 03:27:59
Message-ID: 20100218122759.2355.52131E4D@oss.ntt.co.jp
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


James William Pye <lists(at)jwp(dot)name> wrote:

> Need a special case for the infinities as well?
>
> postgres=# create table foo (d date);
> postgres=# INSERT INTO foo VALUES ('infinity');
> postgres=# COPY foo TO '/Users/jwp/foo.copy' WITH BINARY;
> postgres=# COPY foo FROM '/Users/jwp/foo.copy' WITH BINARY;
> ERROR: date out of range

Exactly. Patch attached.

We have special treatments of infinity in timestamp_recv,
but don't have in date_recv.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center

Attachment Content-Type Size
date_recv_infinity_20100218.patch application/octet-stream 996 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-02-18 03:49:56 Re: [GENERAL] possible bug with inheritance?
Previous Message Bruce Momjian 2010-02-18 03:26:09 Re: NOTIFY/LISTEN on read-only slave?