BUG #1970: Existing /etc/pam.d/postgresql clobbered by RPM install

Hi,

On Mon, 17 Oct 2005, Mark Gibson wrote:

Bug reference: 1970
Logged by: Mark Gibson
Email address: gibsonm@cromwell.co.uk
PostgreSQL version: 8.0.4
Operating system: Redhat Enterprise Linux 4
Description: Existing /etc/pam.d/postgresql clobbered by RPM install
Details:

Hello, I noticed that when installing the 8.0.4 RPM's
it replaced our existing /etc/pam.d/postgresql - this caused our system to
break temporarily, as it was missing the following line:

account required pam_stack.so service=system-auth

I don't know whether this is required for all systems or is just a
peculiarity of our setup, but could the RPM be changed to not clobber this
file in the future. I believe some RPM's install conflicting configs with
the .rpmnew extension. Cheers.

AFAIK, RPMs look for RPM database for the existing files on the system. I
think your file was not generated by any RPM, so our RPM wanted to
replace it.

I can't see any problems with adding

account required pam_stack.so service=system-auth

to our postgresql.pam file. If noone objects, we may release a new
subversion of 8.0.4 with this fix (and elog patch of Tom).

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 Tue Oct 18 19:34:04 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 AB82FD999F;
Tue, 18 Oct 2005 19:01:44 -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 48026-07; Tue, 18 Oct 2005 22:01:41 +0000 (GMT)
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
by svr1.postgresql.org (Postfix) with ESMTP id 9DFF6D99BF;
Tue, 18 Oct 2005 19:01:42 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j9IM1dA6014247;
Tue, 18 Oct 2005 18:01:39 -0400 (EDT)
To: Devrim GUNDUZ <devrim@gunduz.org>
Cc: Mark Gibson <gibsonm@cromwell.co.uk>, pgsql-bugs@postgresql.org,
pgsqlrpms-hackers@postgresql.org
Subject: Re: BUG #1970: Existing /etc/pam.d/postgresql clobbered by
In-reply-to: <Pine.LNX.4.63.0510181637130.9125@mail.kivi.com.tr>
References: <20051017074717.338B4F0D79@svr2.postgresql.org> <Pine.LNX.4.63.0510181637130.9125@mail.kivi.com.tr>
Comments: In-reply-to Devrim GUNDUZ <devrim@gunduz.org>
message dated "Tue, 18 Oct 2005 23:18:04 +0300"
Date: Tue, 18 Oct 2005 18:01:39 -0400
Message-ID: <14246.1129672899@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006]
X-Spam-Level:
X-Archive-Number: 200510/220
X-Sequence-Number: 13201

Devrim GUNDUZ <devrim@gunduz.org> writes:

I can't see any problems with adding
account required pam_stack.so service=system-auth

See also
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167040
which is what inspired this to start with. Not knowing enough about
PAM, I didn't get it right the first time :-(

regards, tom lane

Hi,

On Tue, 18 Oct 2005, Tom Lane wrote:

Devrim GUNDUZ <devrim@gunduz.org> writes:

I can't see any problems with adding
account required pam_stack.so service=system-auth

See also
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167040
which is what inspired this to start with. Not knowing enough about
PAM, I didn't get it right the first time :-(

Ok, I fixed it with

%if %pam
%config(noreplace) /etc/pam.d/postgresql
%endif

in PGDG RPM spec file. However, as I wrote in pgsqlrpms-hackers list, in
PGDG RPMs we can't use include directive in PAM config file since we are
using same spec for all distros.

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 Thu Oct 20 00:07:58 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 18978D9C48
for <pgsql-bugs-postgresql.org@localhost.postgresql.org>; Thu, 20 Oct 2005 00:07:58 -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 48002-08
for <pgsql-bugs-postgresql.org@localhost.postgresql.org>;
Thu, 20 Oct 2005 03:07:56 +0000 (GMT)
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
by svr1.postgresql.org (Postfix) with ESMTP id 12810D7205
for <pgsql-bugs@postgreSQL.org>; Thu, 20 Oct 2005 00:07:55 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j9K37kfk003473;
Wed, 19 Oct 2005 23:07:46 -0400 (EDT)
To: Stanislav Sukholet <ctac@osib.so-cdu.ru>
Cc: pgsql-bugs@postgreSQL.org
Subject: Re: BUG #1976: steps to reproduce BUG #1438: Non UTF-8 client encoding problem
In-reply-to: <200510200808.11883.ctac@osib.so-cdu.ru>
References: <20051019023130.0D4ADF0C4D@svr2.postgresql.org> <22330.1129738328@sss.pgh.pa.us> <200510200808.11883.ctac@osib.so-cdu.ru>
Comments: In-reply-to Stanislav Sukholet <ctac@osib.so-cdu.ru>
message dated "Thu, 20 Oct 2005 08:08:11 +0800"
Date: Wed, 19 Oct 2005 23:07:46 -0400
Message-ID: <3472.1129777666@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006]
X-Spam-Level:
X-Archive-Number: 200510/233
X-Sequence-Number: 13214

Stanislav Sukholet <ctac@osib.so-cdu.ru> writes:

Can't reproduce this here.  What locale settings are you using in the
database?  (Particularly lc_ctype and lc_messages)

mydb=> SHOW client_encoding ;
client_encoding
-----------------
KOI8
(1 запись)

mydb=> show LC_CTYPE;
lc_ctype
-------------
ru_RU.koi8r
(1 запись)

mydb=> show LC_MESSAGES;
lc_messages
-------------
ru_RU.koi8r
(1 запись)

mydb=> CREATE TABLE a (b INTEGER PRIMARY KEY);
ERROR: ignoring unconvertible UTF-8 character 0xd3cf

OK, with that I can reproduce it in 7.4, but more recent releases
produce a bunch of "WARNING: ignoring unconvertible UTF-8 character"
notices and then complete the operation successfully.

This is basically the same problem discussed in this thread:
http://archives.postgresql.org/pgsql-patches/2005-08/msg00037.php
namely that gettext() converts the translated error message to the
encoding implied by LC_CTYPE ... but the error reporting machinery
expects the string to be in the encoding specified for the database.

I have applied a minor tweak to the 7.4 branch to make it behave more
like the later releases, ie you get a WARNING not an ERROR. However
this is certainly not really a solution --- the only reason the behavior
isn't worse is that the ru_RU message catalog doesn't try to translate
"ignoring unconvertible UTF-8 character" and so you don't get into the
recursive failure discussed in the above thread.

The bottom line is that this is one of several reasons why it's a bad
idea to use a database encoding that's incompatible with the underlying
locale settings. I doubt that we'll really be able to fix that until
we replace all our dependence on the C library's locale facilities
... which is something that will probably happen someday, but don't
hold your breath waiting :-(

In short, if you want to use UTF8 database encoding, specify a
UTF8-based locale setting when you initdb. Don't try to change
the database encoding via -E.

regards, tom lane

Mark Gibson wrote:

The following bug has been logged online:

Bug reference: 1970
Logged by: Mark Gibson
Email address: gibsonm@cromwell.co.uk
PostgreSQL version: 8.0.4
Operating system: Redhat Enterprise Linux 4
Description: Existing /etc/pam.d/postgresql clobbered by RPM install
Details:

Hello, I noticed that when installing the 8.0.4 RPM's
it replaced our existing /etc/pam.d/postgresql - this caused our system to
break temporarily, as it was missing the following line:

account required pam_stack.so service=system-auth

I don't know whether this is required for all systems or is just a
peculiarity of our setup, but could the RPM be changed to not clobber this
file in the future. I believe some RPM's install conflicting configs with
the .rpmnew extension. Cheers.

Please report this to the RPM maintainer. We do not create the RPMs.

-- 
  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

Hi,

On Mon, 24 Oct 2005, Bruce Momjian wrote:

<snipped>

Please report this to the RPM maintainer. We do not create the RPMs.

I thought we do? Our RPMs are marked as PGDG RPMs...
--
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 Mon Oct 24 17:59:14 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 F12CCDAC49
for <pgsql-bugs-postgresql.org@localhost.postgresql.org>; Mon, 24 Oct 2005 04:02:57 -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 35997-09
for <pgsql-bugs-postgresql.org@localhost.postgresql.org>;
Mon, 24 Oct 2005 07:02:55 +0000 (GMT)
Received: from smtp-gateway.tataisp.com (smtp-gateway.tataisp.com [203.124.230.5])
by svr1.postgresql.org (Postfix) with SMTP id 7CBB4DAC38
for <pgsql-bugs@postgresql.org>; Mon, 24 Oct 2005 04:02:55 -0300 (ADT)
Received: from yahoo.co.in ([203.196.196.1])
by smtp-gateway.tataisp.com (SMSSMTP 4.1.2.20) with SMTP id M2005102412344331184
for <pgsql-bugs@postgresql.org>; Mon, 24 Oct 2005 12:34:43 +0530
Message-ID: <435C8716.9040104@yahoo.co.in>
Date: Mon, 24 Oct 2005 12:32:46 +0530
From: somesh <somesha_m@yahoo.co.in>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pgsql-bugs@postgresql.org
Subject: access postgresql from GTK+ GUI
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=1.75 required=5 tests=[DNS_FROM_RFC_ABUSE=0.374,
DNS_FROM_RFC_POST=1.376]
X-Spam-Level: *
X-Archive-Number: 200510/277
X-Sequence-Number: 13258

Hi,
Somesh here from Aerospace Systems Pvt Ltd., I am facing some problem in
accessing postgresql database in GTK GUI with Linux environment. Please
can u guide me how to set path for GTK and PostgreSQL to insert and
retrive data from the database, and what are the settings i have to do
for this Redhat linux.

Thank you,
somesh

Am Montag, 24. Oktober 2005 20:27 schrieb Devrim GUNDUZ:

I thought we do? Our RPMs are marked as PGDG RPMs...

You can also mark them "gentoo", but RPM bugs should still ideally be reported
to the RPM builder, not this forum.