From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade and extra_float_digits |
Date: | 2010-05-17 00:18:45 |
Message-ID: | 201005170018.o4H0IjX15856@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> >> Eventually the idea would be to have the build farm run such tests (with
> >> a properly created dump file) so we can learn quickly if the backend
> >> data format is changed.
> >>
> >
> > If we're thinking of doing that, it would be better to back-patch the
> > change that allowed '3'.
> >
> >
> >
>
> Yeah.
>
> It's going to require some fancy dancing to get the buildfarm to do it.
> Each buildfarm run is for a specific branch, and all the built artefacts
> are normally thrown away. I'd have to work out a way of stashing the
> binaries from a build on one branch for use in the pg_upgrade tests in
> the run on another branch. It's doable but could get messy.
Uh, that is not actually a problem. You just need to set
extra_float_digits=-3 to create the dump file, which is only done once
for each major version. You can _load_ that dump file into an
unmodified old cluster and test just fine. I will write up some
instructions in the next few days.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-05-17 00:59:55 | Re: pg_upgrade and extra_float_digits |
Previous Message | Robert Haas | 2010-05-17 00:09:28 | Re: Sort of a planner regression 8.3->8.4 (due to EXISTS inlining) and related stuff |