From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: do we need to postpone beta4? |
Date: | 2010-07-28 23:36:05 |
Message-ID: | 26508.1280360165@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> So now we have the following issues remaining:
> * page corruption after moving tablespace
> * ExplainOnePlan handles snapshots differently than ProcessQuery
> * name and comment of XLogSetAsyncCommitLSN() should be changed
> * Documentation fails to build as PDF
> ...and I wouldn't necessarily regard any of those as forcing another
> beta; the first two are ancient, the third is cosmetic, and the last
> one is a build system issue rather than a code change.
> Obviously, it's too early to decide anything: we may yet discover more
> issues that need to be addressed. But I think we're in much better
> shape than it seemed 24 hours ago.
Yeah. I'm off poking at the "incorrect FTS result" problem, but that
is a pre-existing bug as well; it goes back at least to 8.4 and probably
further.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-07-29 00:25:35 | Re: string_to_array has to be stable? |
Previous Message | Tom Lane | 2010-07-28 23:33:01 | Re: [GENERAL] Incorrect FTS result with GIN index |