| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, "Michael Simms" <grim(at)argh(dot)demon(dot)co(dot)uk> |
| Subject: | Re: [HACKERS] Fixing Simms' vacuum problems |
| Date: | 1999-09-12 00:56:58 |
| Message-ID: | 199909120056.JAA01118@ext16.sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Once we have the changes, the next question is do we want to risk
> back-patching them into 6.5.2? I can see several ways that we could
> proceed:
> 1. Back-patch into REL6_5, and postpone 6.5.2 release for a while
> for beta-testing.
> 2. Put out 6.5.2 now (since it already has several other useful fixes),
> then back-patch, and release 6.5.3 after a beta-testing interval.
> 3. Leave these changes out of 6.5.*, and try to get 6.6 out the door
> soon instead.
>
> I am not eager to hurry 6.6 along --- I have a lot of half-done work
> in the planner/optimizer that I'd like to finish for 6.6. Perhaps
> choice #2 is the way to go. Comments?
Seems #2 is good choice for me too.
---
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 1999-09-12 00:57:04 | Re: [HACKERS] case bug? |
| Previous Message | Tom Lane | 1999-09-12 00:38:21 | Re: [HACKERS] Status report: long-query-string changes |