| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade and extra_float_digits |
| Date: | 2010-05-16 15:31:06 |
| Message-ID: | 1919.1274023866@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Andrew Dunstan wrote:
>> But do earlier server versions accept a value of 3? The 8.4 docs say
>> "The value can be set as high as 2".
> That is the other thing I had to hack --- the 8.4 backend version had to
> be changed to accept '3'. The good thing is this has to be done only
> once --- once I have the dump file, I can use it in testing repeatedly
> because 8.4 does not change.
> 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'.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-16 15:48:21 | Re: Performance problem in textanycat/anytextcat |
| Previous Message | Bruce Momjian | 2010-05-16 13:54:01 | Re: pg_upgrade and extra_float_digits |