| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Reducing NUMERIC size for 8.3 |
| Date: | 2007-06-18 21:27:13 |
| Message-ID: | 7176.1182202033@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Would someone please explain why we are considering this so far past
> features freeze, and who suggtested that the 8.3->8.4 upgrade being a binary
> upgrade was anything more than a pipe dream?
Well, Greg had left further squeezing of numerics as an open item in his
varlena patch, so it's not totally unreasonable to consider a patch for
that now --- as long as it's pretty small and simple.
I agree that in-place upgrade is a pipe dream until we see someone
actually step forward and do the work to build a usable pg_upgrade
utility.
If nothing else, we should consider swapping the n_sign_dscale and
n_weight fields now, since that would enable upward-compatible
implementation of these ideas later. Otherwise any such patch
would probably get rejected if pg_upgrade did happen to emerge out
of nowhere.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-18 21:40:58 | pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |
| Previous Message | Bruce Momjian | 2007-06-18 21:19:15 | Re: Reducing NUMERIC size for 8.3 |