BUG #1926: /etc/init.d/postgresql - script version 7.4.5 fails on startup

Hi,

On Fri, 30 Sep 2005, Kevin Waldron wrote:

The following bug has been logged online:

Bug reference: 1926
Logged by: Kevin Waldron
Email address: kevin@zazzybob.com
PostgreSQL version: 8.0.3
Operating system: CentOS 4.1
Description: /etc/init.d/postgresql - script version 7.4.5 fails on
startup
Details:

I'm using Version 7.4.5 of the postgresql start script (acquired in the
postgresql-8.0.3 rpms for rhel-es-4).

On my HP DL320(G3) server, running CentOS 4.1 (further, detailed specs can,
of course, be provided if required) I have had to modify the sleep at Line
192 from 1 second TO 2 seconds.

Otherwise the test was failing as the postmaster.pid file wasn't written in
time.

See : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=152931

As Tom wrote, increasing the sleep time will work.

I've increased the sleep time from 1 to 2 for PGDG 8.1 beta RPMs. Let's
see what will happen in next beta.

Regards,
--
Devrim GUNDUZ
Kivi Bili�im Teknolojileri - http://www.kivi.com.tr
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org

From pgsql-bugs-owner@postgresql.org Fri Sep 30 11:20:25 2005

X-Original-To: pgsql-bugs-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
by svr1.postgresql.org (Postfix) with ESMTP id 05905D9BA4
for <pgsql-bugs-postgresql.org@localhost.postgresql.org>; Fri, 30 Sep 2005 11:20:08 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
with ESMTP id 90869-09
for <pgsql-bugs-postgresql.org@localhost.postgresql.org>;
Fri, 30 Sep 2005 14:20:03 +0000 (GMT)
Received: from mx-2.sollentuna.net (mx-2.sollentuna.net [195.84.163.199])
by svr1.postgresql.org (Postfix) with ESMTP id 78DCED998A
for <pgsql-bugs@postgresql.org>; Fri, 30 Sep 2005 11:20:05 -0300 (ADT)
Received: from ALGOL.sollentuna.se (janus.sollentuna.se [62.65.68.67])
by mx-2.sollentuna.net (Postfix) with ESMTP
id D294B8F295; Fri, 30 Sep 2005 16:20:09 +0200 (CEST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: BUG #1925: upper() and lower() fails with non-english char.
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Fri, 30 Sep 2005 16:20:09 +0200
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCE6C7A3C@algol.sollentuna.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [BUGS] BUG #1925: upper() and lower() fails with non-english char.
Thread-Index: AcXFwXXZmCrpzzaWRBm7Pc7feCh+EwACHe1Q
From: "Magnus Hagander" <mha@sollentuna.net>
To: =?iso-8859-1?Q?S=C3=B8ren_Vainio?= <s.vainio@mail.dk>,
<pgsql-bugs@postgresql.org>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.061 required=5 tests=[AWL=0.011,
FORGED_RCVD_HELO=0.05]
X-Spam-Level:
X-Archive-Number: 200509/236
X-Sequence-Number: 12976

The following bug has been logged online:
=20
Bug reference: 1925
Logged by: S=C3=B8ren Vainio
Email address: s.vainio@mail.dk
PostgreSQL version: j2sdk1.4.2_07
Operating system: win XP
Description: upper() and lower() fails with non-english char.
Details:=20
=20
upper(string) and lower(string) does not work on danish,=20
swedish and german letters like =C3=A6, =C3=B8, =C3=A5, =C3=BC, and =

=C3=B6=20

(&#230, &#248, &#229, &#252, &#246).

What encoding are you using?
This sounds a lot like what shows up when you use UNICODE (UTF8) =
encoding on a Win32 PostgreSQL 8.0. This is not supported. It will be =
supported in 8.1, but for 8.0 you need to go with a different encoding =
such as LATIN1.

//Magnus

Devrim GUNDUZ <devrim@gunduz.org> writes:

See : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=152931

I've increased the sleep time from 1 to 2 for PGDG 8.1 beta RPMs. Let's
see what will happen in next beta.

I've been using 2 in Red Hat's RPMs for some time. The whole thing is
pretty mystifying though, because there's no way it should take any
significant amount of time for the postmaster to get to the point of
writing its pid-file. It doesn't really do anything except parse its
command-line arguments and the postgresql.conf file before it does that.
I've certainly never been able to reproduce the problem.

It'd be useful to try running the "su" command that launches the
postmaster under "strace -f -tt" to try to gather some information
about why it's so slow. It might be the su rather than the postmaster
per se that's at fault?

regards, tom lane