From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Lockhart <lockhart@fourpalms.org>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tim Hart <tjhart@mac.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [SQL] line datatype
Date: Tue, 16 Jul 2002 09:44:14 -0400
Message-ID: <12277.1026827054@sss.pgh.pa.us> (raw)
In-Reply-To: <3D33B8D5.D8A2E1CE@fourpalms.org>
References: <200207160333.g6G3Xnc22777@candle.pha.pa.us>
<3D33B8D5.D8A2E1CE@fourpalms.org>
Thomas Lockhart <lockhart@fourpalms.org> writes:
> The issue is in choosing an external format for LINE which does not lose
> precision during dump/reload.
Why is this any worse for LINE than for any of the other geometric
types (or for plain floats, for that matter)?
We do need a solution for exact dump/reload of floating-point data,
but I don't see why the lack of it should be reason to disable access
to the LINE type.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, lockhart@fourpalms.org, pgman@candle.pha.pa.us, tjhart@mac.com, pgsql-hackers@postgresql.org
Subject: Re: [SQL] line datatype
In-Reply-To: <12277.1026827054@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox