| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Numeric 508 datatype |
| Date: | 2005-11-17 17:48:45 |
| Message-ID: | 29323.1132249725@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-patches |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> If the patch is accepted technically, in can be applied at any time,
> right up to code freeze for this or the next release. It's a fairly
> independent patch.
> I'd suggest we check it out now, then put it in a holding pen for awhile
> to see if an upgrade tool emerges.
I'm disinclined to do that unless there's a pretty firm commitment from
someone to work on pg_upgrade in the near future. Patches that are not
in the tree tend to suffer from code drift; if we wait six months or a
year to apply what you've done then we'll likely be looking at
significantly more work to get it in. We'd also be losing the direct
and indirect testing that the patch would get were it in the tree over
that length of time.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Atkins | 2005-11-17 17:53:26 | unsubscribe pgsql-general |
| Previous Message | Tom Lane | 2005-11-17 17:43:34 | Re: strange behavior on 8.1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-17 17:51:39 | Re: [HACKERS] ERROR: could not read block |
| Previous Message | Kevin Grittner | 2005-11-17 17:39:20 | Re: [HACKERS] ERROR: could not read block |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2005-11-17 18:06:36 | Re: Numeric 508 datatype |
| Previous Message | Simon Riggs | 2005-11-17 16:59:43 | Re: Numeric 508 datatype |