pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Joris van Zwieten <vanzwieten@stcorp.nl>
Cc: Jeroen T. Vermeulen <jtv@xs4all.nl>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Array handling in libpq
Date: Wed, 17 Jan 2007 11:20:59 -0600
Message-ID: <20070117172059.GA13308@wolff.to> (raw)
In-Reply-To: <54258.192.87.1.229.1169023509.squirrel@control.prolocation.net>
References: <200701170346.l0H3kBd23330@momjian.us>
	<5050.125.24.240.25.1169016593.squirrel@webmail.xs4all.nl>
	<54258.192.87.1.229.1169023509.squirrel@control.prolocation.net>

On Wed, Jan 17, 2007 at 09:45:09 +0100,
  Joris van Zwieten <vanzwieten@stcorp.nl> wrote:
> 
> Thanks for your replies. This is good to know, although one worry remains
> and that is loss of precision in the conversion of double to string. But
> this could probably always be solved by using enough digits in the
> conversion, right?

There is a GUC variable (extra_float_digits) for doing this. Setting it to 2
will give enough extra decimal places that you should get back the same
binary representation (on the same architecture). This is automatically used
in some cases (e.g. pgdump).



view thread (8+ messages)  latest in thread

Message-ID: <20070117172059.GA13308@wolff.to>
Permalink:  ../20070117172059.GA13308@wolff.to/
Also on:    postgresql.org/message-id/20070117172059.GA13308@wolff.to

 · 

reply

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-interfaces@postgresql.org
  Cc: bruno@wolff.to, vanzwieten@stcorp.nl, jtv@xs4all.nl, bruce@momjian.us
  Subject: Re: Array handling in libpq
  In-Reply-To: <20070117172059.GA13308@wolff.to>

* 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