Re: Re: Command Prompt 8.4.4 PRMs compiled with debug/assert enabled

Lacey Powers wrote:
> I tried to send something out Thursday about this to pgsql-performance,
> and I tried to send something out last night about this to
> pgsql-announce. Neither seem to have gotten through, or approved. =( =( =(

Yes, I suspected that might have happened.

> Thursday to the Performance List:
>
> Hello Everyone,
>
> New packages for 8.4.4 on CentOS 5.5 and RHEL 5.5 (all arches), have
> been built, and are available in the PGDG repo.
>
> http://yum.pgsqlrpms.org/8.4/redhat/rhel-5-i386/
> http://yum.pgsqlrpms.org/8.4/redhat/rhel-5-x86_64/
...
> Again, I extend deep apologies for the inconvenience.
>
> If there is anything further we can help with, please let us know.

Do any of the other minor releases made at the same time have this
problem, or just 8.4.4?

> And last night, for a public announcement:
>
>
> Dear PostgreSQL RPMS users,
>
> There was a mistake with the 8.4.4 packages resulting in --enable-debug
> and --enable-cassert being enabled in the packages for CentOS 5.5 x86_64
> and i386.
>
> This has been corrected in the 8.4.4-2PGDG packages, which are in the
> PostgreSQL RPMS repository.
>
> Please update to these corrected packages as soon as possible.
>
> We apologize for any inconvenience.

OK, do the Yum folks get these updates automatically?

> I had this fixed and out in the repo about an hour after I was made
> aware of it (Alvaro let me know at ~9:30AM PDT ( Thank you *so* much,
> Alvaro! =) ), and I had things out at ~10:45AM PDT, and tried to reply
> shortly thereafter. =( ), and tried to let people know as best I could.
>
> I know there are a great deal of concerns regarding this, and I am
> greatly sorry for any trouble that was caused, and will add tests to the
> build process to ensure that this does not happen again. =(
>
> Given the concern, I thought I'd try posting a reply here, to this
> email, to soothe fears, and to plead for some moderator help, since both
> of my emails are most likely stuck in moderation. =( =(
>
> Again, I'm sorry for the issues I caused, and I will endeavor to make
> the turnaround and notification time quicker in the future. =(
>
> If there are further questions, or needs, please let me know, and I will
> try to get them addressed as soon as I can.

OK, how do we properly get rid of all those buggy 8.4.4 installs? Seems
a posting to announce is not enough, and we need to show users how to
tell if they are running a de-buggy version. Does the fixed 8.4.4
install have a different visible version number, or do they have to use
SHOW debug_assertions?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ None of us is going to be here forever. +