We have had very few beta1 issues. I am thinking we should release
beta2 next week and perhaps accelerate beta and consider a final release
in November rather than December. Because of the length of our feature
freeze it is possible we are not going to have as many beta bugs.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

A Diumenge 21 Octubre 2007, Bruce Momjian va escriure:
> We have had very few beta1 issues. I am thinking we should release
> beta2 next week and perhaps accelerate beta and consider a final release
> in November rather than December. Because of the length of our feature
> freeze it is possible we are not going to have as many beta bugs.

I want to send a patch for the contrib modules by late sunday (europe here .
I'm doing some cleanup and organizing it a bit better and I think somebody
expected these docs to be in the second beta...

--
Albert Cervera i Areny
http://www.NaN-tic.com

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Bruce Momjian <bruce@momjian.us> writes:
> We have had very few beta1 issues. I am thinking we should release
> beta2 next week and perhaps accelerate beta and consider a final release
> in November rather than December. Because of the length of our feature
> freeze it is possible we are not going to have as many beta bugs.

We need to deal with the open questions about tsearch API before beta2.
Since we've already forced initdb for beta2, there's no cost to
additional system-catalog changes now, but that window will clang shut
again when beta2 goes out.

I'm disappointed that Oleg and Teodor haven't commented on those issues
yet ...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Bruce Momjian wrote:
> We have had very few beta1 issues. I am thinking we should release
> beta2 next week and perhaps accelerate beta and consider a final release
> in November rather than December. Because of the length of our feature
> freeze it is possible we are not going to have as many beta bugs.
>

Unfortunately, I think that's because people haven't been testing. At
my keynote at the PostgreSQL Fall Conference yesterday, I asked the
audience of 63 people how many had built 8.3 beta and tried to run
something on it ... 3. And these are our enthusiasts.

For me, I ran into a CC compile issues on Solaris (diagnosing now) and
haven't got much further on testing it there, although Jignesh is
already into performance testing. Worked fine for demo purposes on
OSX.4, though, and I was able to import some old databases (Staffos,
TPCE) without unexpected issues.

Of course I would like to do a short beta, but I think we need to harass
people to test more.

--Josh

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Josh Berkus wrote:
> Bruce Momjian wrote:
> > We have had very few beta1 issues. I am thinking we should release
> > beta2 next week and perhaps accelerate beta and consider a final release
> > in November rather than December. Because of the length of our feature
> > freeze it is possible we are not going to have as many beta bugs.
> >
>
> Unfortunately, I think that's because people haven't been testing. At
> my keynote at the PostgreSQL Fall Conference yesterday, I asked the
> audience of 63 people how many had built 8.3 beta and tried to run
> something on it ... 3. And these are our enthusiasts.
>
> For me, I ran into a CC compile issues on Solaris (diagnosing now) and
> haven't got much further on testing it there, although Jignesh is
> already into performance testing. Worked fine for demo purposes on
> OSX.4, though, and I was able to import some old databases (Staffos,
> TPCE) without unexpected issues.
>
> Of course I would like to do a short beta, but I think we need to harass
> people to test more.

Nothing motivates people to test more than moving toward RC1. ;-)

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Bruce Momjian wrote:
> Josh Berkus wrote:
>> Bruce Momjian wrote:
>>> We have had very few beta1 issues. I am thinking we should release
>>> beta2 next week and perhaps accelerate beta and consider a final release
>>> in November rather than December. Because of the length of our feature
>>> freeze it is possible we are not going to have as many beta bugs.
>>>
>> Unfortunately, I think that's because people haven't been testing. At
>> my keynote at the PostgreSQL Fall Conference yesterday, I asked the
>> audience of 63 people how many had built 8.3 beta and tried to run
>> something on it ... 3. And these are our enthusiasts.
>>
>> For me, I ran into a CC compile issues on Solaris (diagnosing now) and
>> haven't got much further on testing it there, although Jignesh is
>> already into performance testing. Worked fine for demo purposes on
>> OSX.4, though, and I was able to import some old databases (Staffos,
>> TPCE) without unexpected issues.
>>
>> Of course I would like to do a short beta, but I think we need to harass
>> people to test more.
>
> Nothing motivates people to test more than moving toward RC1. ;-)
>

Getting Beta2 out is vital to actually getting people to test there are
known issues and changes with Beta1 that have made it pretty much a
useless Beta.

Sincerely,

Joshua D. Drake



---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

"Joshua D. Drake" <jd@commandprompt.com> writes:
> Bruce Momjian wrote:
>> Nothing motivates people to test more than moving toward RC1. ;-)

> Getting Beta2 out is vital to actually getting people to test there are
> known issues and changes with Beta1 that have made it pretty much a
> useless Beta.

Agreed --- at this point we know we've forced initdb, plus there are
those known locale issues on Windows, so it's a bit hard to ask someone
to install beta1 if they haven't already. I think what we need to do
next is get to closure on the open issues and get a beta2 out ASAP.

I've posted notes over the past few days about half a dozen relatively-
minor-but-none-the-less-initdb-forcing issues in tsearch. We have to
either fix those or decide we're not going to fix them. I'm a bit
annoyed that Oleg and Teodor haven't responded to any of those comments.

I'm also not totally clear on whether we are happy with the Windows
locale situation yet. Comments from the Win32 contingent?

Can anyone think of any other issues that should be considered beta2
stoppers? (No, the contrib documentation isn't one...)

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



- --On Sunday, October 21, 2007 22:38:04 -0400 Tom Lane <tgl@sss.pgh.pa.us>
wrote:

> I've posted notes over the past few days about half a dozen relatively-
> minor-but-none-the-less-initdb-forcing issues in tsearch. We have to
> either fix those or decide we're not going to fix them. I'm a bit
> annoyed that Oleg and Teodor haven't responded to any of those comments.

Remove the tsearch2 stuff if we can't even get feedback from the developers at
such a critical time?

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHHCqo4QvfyHIvDvMRAjoYAJ9h0wSieG/NGKIVjxs5yEw3BEifrwCffGv6
A8oeYWF3Ophv+RwD2dWzgLw=
=tuCo
-----END PGP SIGNATURE-----


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

"Marc G. Fournier" <scrappy@hub.org> writes:
> On Sunday, October 21, 2007 22:38:04 -0400 Tom Lane <tgl@sss.pgh.pa.us>
> wrote:
>> I've posted notes over the past few days about half a dozen relatively-
>> minor-but-none-the-less-initdb-forcing issues in tsearch. We have to
>> either fix those or decide we're not going to fix them. I'm a bit
>> annoyed that Oleg and Teodor haven't responded to any of those comments.

> Remove the tsearch2 stuff if we can't even get feedback from the developers at
> such a critical time?

I don't want to go that far. But I will start making changes on my own
authority if I don't hear objections pretty soon ...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

>
> - --On Sunday, October 21, 2007 22:38:04 -0400 Tom Lane <tgl@sss.pgh.pa.us>
> wrote:
>
> > I've posted notes over the past few days about half a dozen relatively-
> > minor-but-none-the-less-initdb-forcing issues in tsearch. We have to
> > either fix those or decide we're not going to fix them. I'm a bit
> > annoyed that Oleg and Teodor haven't responded to any of those comments.
>
> Remove the tsearch2 stuff if we can't even get feedback from the developers at
> such a critical time?
>

It's little bit hard. TSearch2 was strongly refactorised by Tom, and
current Tom's questions are practical, but not fundamental.

Pavel

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend