| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tim Hart <tjhart(at)mac(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [SQL] line datatype |
| Date: | 2002-07-16 13:44:14 |
| Message-ID: | 12277.1026827054@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Thomas Lockhart <lockhart(at)fourpalms(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2002-07-16 14:22:20 | Re: pg_views.definition |
| Previous Message | Tom Lane | 2002-07-16 13:31:47 | Re: pg_views.definition |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-07-16 15:21:05 | Re: [SQL] line datatype |
| Previous Message | Bruno Wolff III | 2002-07-16 11:45:53 | Re: Indexing UNIONs |