Beta2 Tag'd and Bundled ...
Everything looks like it built clean ... will do a quick, more general
announce tomorrow, but if someone can confirm that things are good, that
would be great ...
--On Wednesday, August 27, 2003 00:21:23 -0300 "Marc G. Fournier"
<scrappy@postgresql.org> wrote:
Everything looks like it built clean ... will do a quick, more general
announce tomorrow, but if someone can confirm that things are good, that
would be great ...
My UnixWare Thread.c patch/fix has been IGNORED.
I'd like to see a fix before we declare Beta2.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Larry Rosenman <ler@lerctr.org> writes:
My UnixWare Thread.c patch/fix has been IGNORED.
I'd like to see a fix before we declare Beta2.
Beta2 is a done deal. When Bruce gets back from the seashore I expect
he'll take a look at the issues you raised, but we're not holding off
beta2 another week for that to happen.
regards, tom lane
--On Thursday, August 28, 2003 01:06:46 -0400 Tom Lane <tgl@sss.pgh.pa.us>
wrote:
Larry Rosenman <ler@lerctr.org> writes:
My UnixWare Thread.c patch/fix has been IGNORED.
I'd like to see a fix before we declare Beta2.Beta2 is a done deal. When Bruce gets back from the seashore I expect
he'll take a look at the issues you raised, but we're not holding off
beta2 another week for that to happen.
I was under the impression he was working on it.
We are shipping a broken template/unixware due to bad spaces....
regards, tom lane
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Tom Lane writes:
Beta2 is a done deal. When Bruce gets back from the seashore I expect
he'll take a look at the issues you raised, but we're not holding off
beta2 another week for that to happen.
Could someone tell the rest of the world ahead of time when release steps
are going to happen?
--
Peter Eisentraut peter_e@gmx.net
--On Thursday, August 28, 2003 19:31:17 +0200 Peter Eisentraut
<peter_e@gmx.net> wrote:
Tom Lane writes:
Beta2 is a done deal. When Bruce gets back from the seashore I expect
he'll take a look at the issues you raised, but we're not holding off
beta2 another week for that to happen.Could someone tell the rest of the world ahead of time when release steps
are going to happen?
AND make sure key people are *NOT UNAVAILABLE* for issues?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Larry Rosenman wrote:
--On Thursday, August 28, 2003 19:31:17 +0200 Peter Eisentraut
<peter_e@gmx.net> wrote:Tom Lane writes:
Beta2 is a done deal. When Bruce gets back from the seashore I expect
he'll take a look at the issues you raised, but we're not holding off
beta2 another week for that to happen.Could someone tell the rest of the world ahead of time when release steps
are going to happen?AND make sure key people are *NOT UNAVAILABLE* for issues?
Larry, you keep going in this direction and I will think about pulling
thread support for Unixware, and the rest of the group might cheer! (SCO
== Unixware) In fact, my just saying someone else has to handle the
Unixware threading issues might kill it right there.
For the record, per platform threading will probably be in flux even
after the final release as we adjust thing for various threading
libraries/flags.
OK, back to the 1k emails that arrived in the last two days.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073Larry Rosenman wrote:
--On Thursday, August 28, 2003 01:06:46 -0400 Tom Lane <tgl@sss.pgh.pa.us>
wrote:Larry Rosenman <ler@lerctr.org> writes:
My UnixWare Thread.c patch/fix has been IGNORED.
I'd like to see a fix before we declare Beta2.Beta2 is a done deal. When Bruce gets back from the seashore I expect
he'll take a look at the issues you raised, but we're not holding off
beta2 another week for that to happen.I was under the impression he was working on it.
We are shipping a broken template/unixware due to bad spaces....
What bad spaces? Have you looked at current CVS that went into 7.4?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073--On Friday, August 29, 2003 22:58:50 -0400 Bruce Momjian
<pgman@candle.pha.pa.us> wrote:
Larry Rosenman wrote:
--On Thursday, August 28, 2003 19:31:17 +0200 Peter Eisentraut
<peter_e@gmx.net> wrote:Tom Lane writes:
Beta2 is a done deal. When Bruce gets back from the seashore I expect
he'll take a look at the issues you raised, but we're not holding off
beta2 another week for that to happen.Could someone tell the rest of the world ahead of time when release
steps are going to happen?AND make sure key people are *NOT UNAVAILABLE* for issues?
Larry, you keep going in this direction and I will think about pulling
thread support for Unixware, and the rest of the group might cheer! (SCO
== Unixware) In fact, my just saying someone else has to handle the
Unixware threading issues might kill it right there.For the record, per platform threading will probably be in flux even
after the final release as we adjust thing for various threading
libraries/flags.OK, back to the 1k emails that arrived in the last two days.
Don't start on the SCO issue. I submitted patches last weekend to fix the
UnixWare (and possibly other) issues.
You said you were working on them, then I see the note that BETA2 was tagged
with INVALID shell code in src/templates/unixware, and
the per-platform threading stuff BROKEN on UnixWare.
When I left for Las Vegas on 8/16, it was **WORKING**. You committed a
change
that BROKE it again.
Yes, I'm pissed.
UnixWare==SCO, but the Court fight has **NOTHING** to do with this issue.
Does the PG core not care anymore about **QUALITY**?
I'm NOT going to stand idly by as the SCO/IBM/RED HAT Legal issues are used
to
hurt PostgreSQL's quality.
I'm NOT very pleased.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
--On Friday, August 29, 2003 23:00:46 -0400 Bruce Momjian
<pgman@candle.pha.pa.us> wrote:
Larry Rosenman wrote:
--On Thursday, August 28, 2003 01:06:46 -0400 Tom Lane
<tgl@sss.pgh.pa.us> wrote:Larry Rosenman <ler@lerctr.org> writes:
My UnixWare Thread.c patch/fix has been IGNORED.
I'd like to see a fix before we declare Beta2.Beta2 is a done deal. When Bruce gets back from the seashore I expect
he'll take a look at the issues you raised, but we're not holding off
beta2 another week for that to happen.I was under the impression he was working on it.
We are shipping a broken template/unixware due to bad spaces....
What bad spaces? Have you looked at current CVS that went into 7.4?
SUPPORTS_THREADS=yes
NEED_REENTRANT_FUNC_NAMES=yes
THREAD_CFLAGS = "$THREAD_CFLAGS -D_REENTRANT"
$
note the last line before the prompt.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Does the PG core not care anymore about **QUALITY**?
Ummm, I believe that is why we are still in Beta, and not at a Release
Candidate stage ... cause there are still bugs, with Unixware obviously
being one of them ...
--On Saturday, August 30, 2003 00:09:51 -0300 "Marc G. Fournier"
<scrappy@hub.org> wrote:
Does the PG core not care anymore about **QUALITY**?
Ummm, I believe that is why we are still in Beta, and not at a Release
Candidate stage ... cause there are still bugs, with Unixware obviously
being one of them ...
So be it, but I was under the impression that the fix would be committed
shortly after
I posted it on LAST SATURDAY, but apparently Bruce was out of town, and the
Beta2 TAG
was laid, WITHOUT PUBLIC NOTICE about the TAG coming.
Then the SCO/IBM/RED HAT lawsuits are thrown in my face for complaining
about these facts.
I want to see PostgreSQL succeed and take over the Open Source DataBase
world, and
want to help, but y'all are making it HARD.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Larry Rosenman wrote:
Don't start on the SCO issue. I submitted patches last weekend to fix the
UnixWare (and possibly other) issues.You said you were working on them, then I see the note that BETA2 was tagged
with INVALID shell code in src/templates/unixware, and
the per-platform threading stuff BROKEN on UnixWare.When I left for Las Vegas on 8/16, it was **WORKING**. You committed a
change
that BROKE it again.Yes, I'm pissed.
UnixWare==SCO, but the Court fight has **NOTHING** to do with this issue.
Does the PG core not care anymore about **QUALITY**?
I'm NOT going to stand idly by as the SCO/IBM/RED HAT Legal issues are used
to
hurt PostgreSQL's quality.I'm NOT very pleased.
SCO's threading support in a beta release is about number 2000 on my
list of priorities right now. It will work in final --- that's all I
can promise. If that isn't good enough, find someone else who wants to
do the work for you.
I am avoiding fixing the SCO port because it would ugilify the other
ports --- we need to discuss that, not ram in a fix just to get it
working on one platform --- that is quality.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073--On Friday, August 29, 2003 23:17:50 -0400 Bruce Momjian
<pgman@candle.pha.pa.us> wrote:
Larry Rosenman wrote:
Don't start on the SCO issue. I submitted patches last weekend to fix
the UnixWare (and possibly other) issues.You said you were working on them, then I see the note that BETA2 was
tagged with INVALID shell code in src/templates/unixware, and
the per-platform threading stuff BROKEN on UnixWare.When I left for Las Vegas on 8/16, it was **WORKING**. You committed a
change
that BROKE it again.Yes, I'm pissed.
UnixWare==SCO, but the Court fight has **NOTHING** to do with this issue.
Does the PG core not care anymore about **QUALITY**?
I'm NOT going to stand idly by as the SCO/IBM/RED HAT Legal issues are
used to
hurt PostgreSQL's quality.I'm NOT very pleased.
SCO's threading support in a beta release is about number 2000 on my
list of priorities right now. It will work in final --- that's all I
can promise. If that isn't good enough, find someone else who wants to
do the work for you.I am avoiding fixing the SCO port because it would ugilify the other
ports --- we need to discuss that, not ram in a fix just to get it
working on one platform --- that is quality.
where is the discussion happening?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
So be it, but I was under the impression that the fix would be committed
shortly after I posted it on LAST SATURDAY, but apparently Bruce was out
of town, and the Beta2 TAG was laid, WITHOUT PUBLIC NOTICE about the TAG
coming.
Beta2 TAG was laid so that we could wrap up all fixes to date, of which
yours for unixware hadn't been included yet ... it had been 3 weeks since
Beta1, there were alot of changes, and if ppl are testing based on the tar
ball and not straight CVS, chances are most bugs reported had already been
fixed ...
Then the SCO/IBM/RED HAT lawsuits are thrown in my face for complaining
about these facts.
This was uncalled for, but so were your comments over one patch ...
I want to see PostgreSQL succeed and take over the Open Source DataBase
world, and want to help, but y'all are making it HARD.
Because one patch wasn't committed before we tar'd up a new beta?
Larry Rosenman wrote:
--On Friday, August 29, 2003 23:00:46 -0400 Bruce Momjian
<pgman@candle.pha.pa.us> wrote:Larry Rosenman wrote:
--On Thursday, August 28, 2003 01:06:46 -0400 Tom Lane
<tgl@sss.pgh.pa.us> wrote:Larry Rosenman <ler@lerctr.org> writes:
My UnixWare Thread.c patch/fix has been IGNORED.
I'd like to see a fix before we declare Beta2.Beta2 is a done deal. When Bruce gets back from the seashore I expect
he'll take a look at the issues you raised, but we're not holding off
beta2 another week for that to happen.I was under the impression he was working on it.
We are shipping a broken template/unixware due to bad spaces....
What bad spaces? Have you looked at current CVS that went into 7.4?
SUPPORTS_THREADS=yes
NEED_REENTRANT_FUNC_NAMES=yes
THREAD_CFLAGS = "$THREAD_CFLAGS -D_REENTRANT"
$note the last line before the prompt.
Oh, sorry. Fixed now. I am always thinking that is a makefile when it
isn't.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073SUPPORTS_THREADS=yes
NEED_REENTRANT_FUNC_NAMES=yes
THREAD_CFLAGS = "$THREAD_CFLAGS -D_REENTRANT"
$note the last line before the prompt.
Check current CVS ... now that Bruce has caught up on his email (or made a
dent in it) after being away, looks like he's committed the fix:
SUPPORTS_THREADS=yes
NEED_REENTRANT_FUNC_NAMES=yes
THREAD_CFLAGS="$THREAD_CFLAGS -D_REENTRANT"
Larry Rosenman wrote:
UnixWare==SCO, but the Court fight has **NOTHING** to do with this issue.
Does the PG core not care anymore about **QUALITY**?
I'm NOT going to stand idly by as the SCO/IBM/RED HAT Legal issues are
used to
hurt PostgreSQL's quality.I'm NOT very pleased.
SCO's threading support in a beta release is about number 2000 on my
list of priorities right now. It will work in final --- that's all I
can promise. If that isn't good enough, find someone else who wants to
do the work for you.I am avoiding fixing the SCO port because it would ugilify the other
ports --- we need to discuss that, not ram in a fix just to get it
working on one platform --- that is quality.where is the discussion happening?
That's the problem --- I haven't even had time to collect the
information and post it for comment yet.
Quality is getting the right right, not necessary quickly. You fix was
put on hold because it was complex (for other platforms) and other
things had higher priority.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073Marc G. Fournier wrote:
SUPPORTS_THREADS=yes
NEED_REENTRANT_FUNC_NAMES=yes
THREAD_CFLAGS = "$THREAD_CFLAGS -D_REENTRANT"
$note the last line before the prompt.
Check current CVS ... now that Bruce has caught up on his email (or made a
dent in it) after being away, looks like he's committed the fix:SUPPORTS_THREADS=yes
NEED_REENTRANT_FUNC_NAMES=yes
THREAD_CFLAGS="$THREAD_CFLAGS -D_REENTRANT"
I didn't realize that space was there until he just posted it --- that I
could have fixed easily.
The major holding point is that SCO is going to require we specify each
*_r function required for threading. SCO doesn't have strerror_r, but
needs the others. That is going to be three functions call options to
be defined per platform we support. I need to know the cleanest way of
attacking that, so I don't break more platforms.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073--On Saturday, August 30, 2003 00:21:29 -0300 "Marc G. Fournier"
<scrappy@hub.org> wrote:
SUPPORTS_THREADS=yes
NEED_REENTRANT_FUNC_NAMES=yes
THREAD_CFLAGS = "$THREAD_CFLAGS -D_REENTRANT"
$note the last line before the prompt.
Check current CVS ... now that Bruce has caught up on his email (or made a
dent in it) after being away, looks like he's committed the fix:SUPPORTS_THREADS=yes
NEED_REENTRANT_FUNC_NAMES=yes
THREAD_CFLAGS="$THREAD_CFLAGS -D_REENTRANT"
he just sent me a note. That post was from AnonCVS right before I posted.
If what's above is what's in cvs now, we're fine, but we still can't
--enable-thread-safety
due to the code in thread.c.
I'll shut up now.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
