From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: pg_upgrade and extra_float_digits |
Date: | 2010-05-16 02:44:46 |
Message-ID: | 201005160244.o4G2ikP12390@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
> > FYI, I test pg_upgrade by loading the old cluster's regression database
> > from a pg_dump output file, then after the upgrade, I dump the
> > regression database of the new cluster and diff the changes.
> >
> > The problem I just encountered is that pg_dump uses
> > extra_float_digits=-3 for 9.0, while previous releases used '2'. I had
> > to do hack each server version to get a dump output that would match
> > without rounding errors --- it did eventually work and validated.
> >
> >
>
> That sounds like a disaster waiting to happen. The server version is
> going to affect much more than just this behaviour, surely. Wouldn't it
> be better to provide a pg_dump option to provide the extra_float_digits
> setting?
FYI, you can't override it with PGOPTIONS because it is set inside the
pg_dump binary. I am not sure what you mean by your second sentence.
I was just reporting it in case anyone else was trying this for testing.
I doubt anyone else is going to try such a thing.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-05-16 02:46:43 | Re: pg_upgrade and extra_float_digits |
Previous Message | Andrew Dunstan | 2010-05-16 02:42:15 | Re: pg_upgrade and extra_float_digits |