From: | Lacey Powers <lacey(dot)powers(at)commandprompt(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Subject: | Re: Re: Command Prompt 8.4.4 PRMs compiled with debug/assert enabled |
Date: | 2010-06-14 16:06:55 |
Message-ID: | 4C16539F.3040502@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Bruce Momjian wrote:
> Bruce Momjian wrote:
>> Bruce Momjian wrote:
>>> Bruce Momjian wrote:
>>>> Alvaro Herrera wrote:
>>>>> Excerpts from Tom Lane's message of jue jun 10 11:46:25 -0400 2010:
>>>>>
>>>>>> Yes, the folks at commandprompt need to be told about this. Loudly.
>>>>>> It's a serious packaging error.
>>>>> Just notified Lacey, the packager (not so loudly, though); she's working
>>>>> on new packages, and apologizes for the inconvenience.
>>>> [ Thread moved to hackers. 8.4.4 RPMs were built with debug flags. ]
>>>>
>>>> Uh, where arIf there are further questions, or needs, please let me know, and I will try to get them addressed as soon as I can.e we on this? Has it been completed? How are people
>>>> informed about this? Do we need to post to the announce email list?
>>>> Does Yum just update them? How did this mistake happen? How many days
>>>> did it take to detect the problem?
>>>>
>>>> Why has no news been posted here?
>>>>
>>>> https://public.commandprompt.com/projects/pgcore/news
>>> Why have I received no reply to this email? Do people think this is not
>>> a serious issue? I know it is a weekend but the problem was identified
>>> on Thursday, meaning there was a full workday for someone from
>>> CommandPrompt to reply to the issue and report a status:
>>>
>>> http://archives.postgresql.org/pgsql-performance/2010-06/msg00165.php
>> [ Updated subject line.]
>>
>> I am on IM with Joshua Drake right now and am working to get answers to
>> the questions above. He or I will report in the next few hours.
>>
>> FYI, only Command Prompt-produced RPMs are affected. Devrim's RPMs are
>> not:
>>
>> http://yum.postgresqlrpms.org/
>
> I have still seen no public report about this, 12 hours after talking to
> Josh Drake on IM about it. :-(
>
Hello Everyone,
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. =( =( =(
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/
Output from pg_config --configure --version is below.
x86_64:
'--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu'
'--target=x86_64-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr'
'--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin'
'--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include'
'--libdir=/usr/lib64' '--libexecdir=/usr/libexec' '--localstatedir=/var'
'--sharedstatedir=/usr/com' '--mandir=/usr/share/man'
'--infodir=/usr/share/info' '--disable-rpath' '--with-perl'
'--with-python' '--with-tcl' '--with-tclconfig=/usr/lib64'
'--with-openssl' '--with-pam' '--with-krb5' '--with-gssapi'
'--with-includes=/usr/include' '--with-libraries=/usr/lib64'
'--enable-nls' '--enable-thread-safety' '--with-libxml' '--with-libxslt'
'--with-ldap' '--with-system-tzdata=/usr/share/zoneinfo'
'--sysconfdir=/etc/sysconfig/pgsql' '--datadir=/usr/share/pgsql'
'--with-docdir=/usr/share/doc' 'build_alias=x86_64-redhat-linux-gnu'
'host_alias=x86_64-redhat-linux-gnu'
'target_alias=x86_64-redhat-linux-gnu' 'CFLAGS=-O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -I/usr/include/et'
'CPPFLAGS= -I/usr/include/et'
PostgreSQL 8.4.4
i386:
'--build=i686-redhat-linux-gnu' '--host=i686-redhat-linux-gnu'
'--target=i386-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr'
'--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin'
'--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include'
'--libdir=/usr/lib' '--libexecdir=/usr/libexec' '--localstatedir=/var'
'--sharedstatedir=/usr/com' '--mandir=/usr/share/man'
'--infodir=/usr/share/info' '--disable-rpath' '--with-perl'
'--with-python' '--with-tcl' '--with-tclconfig=/usr/lib'
'--with-openssl' '--with-pam' '--with-krb5' '--with-gssapi'
'--with-includes=/usr/include' '--with-libraries=/usr/lib'
'--enable-nls' '--enable-thread-safety' '--with-libxml' '--with-libxslt'
'--with-ldap' '--with-system-tzdata=/usr/share/zoneinfo'
'--sysconfdir=/etc/sysconfig/pgsql' '--datadir=/usr/share/pgsql'
'--with-docdir=/usr/share/doc' 'build_alias=i686-redhat-linux-gnu'
'host_alias=i686-redhat-linux-gnu' 'target_alias=i386-redhat-linux-gnu'
'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
-mtune=generic -fasynchronous-unwind-tables -I/usr/include/et'
'CPPFLAGS= -I/usr/include/et'
PostgreSQL 8.4.4
Again, I extend deep apologies for the inconvenience.
If there is anything further we can help with, please let us know.
Regards,
Lacey
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.
Regards,
Lacey
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.
Apologies,
Lacey
--
Lacey Powers
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 ext 104
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2010-06-14 16:11:29 | Re: warning message in standby |
Previous Message | Greg Stark | 2010-06-14 15:51:26 | Re: pg_archive_bypass |
From | Date | Subject | |
---|---|---|---|
Next Message | MUHAMMAD ASIF | 2010-06-14 18:28:01 | RE: [PERFORM] Dbt2 with postgres issues on CentOS-5.3 |
Previous Message | Dave Crooke | 2010-06-14 15:58:20 | Re: Fwd: Dead lock |