Password for postgresql superuser?
Is there any security risk in the postgresql superuser having a password?
I installed a Linux distro recently and had it install Postgresql. It automatically set up the postgres account; the account was set up with no password.
I could of course create a password, but it's not clear to me that's a good thing from a security standpoint.
From pgsql-general-owner@postgresql.org Thu Jun 8 11:57:55 2006
X-Original-To: pgsql-general-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
by postgresql.org (Postfix) with ESMTP id C44869FA5C8
for <pgsql-general-postgresql.org@postgresql.org>; Thu, 8 Jun 2006 11:57:54 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
with ESMTP id 63882-05 for <pgsql-general-postgresql.org@postgresql.org>;
Thu, 8 Jun 2006 11:57:45 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191])
by postgresql.org (Postfix) with ESMTP id 2A0A89F9EF3
for <pgsql-general@postgresql.org>; Thu, 8 Jun 2006 11:57:44 -0300 (ADT)
Received: by nf-out-0910.google.com with SMTP id l37so368341nfc
for <pgsql-general@postgresql.org>; Thu, 08 Jun 2006 07:57:42 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:mime-version:content-type;
b=RZ1De92wne3Q4HJaDkJgml1gZ7NtQMWKYujG1mKUJ4N+ZyoyLshgf1pKAkyJ2eB8aEwD2+pO8LLwkQX9fnHx+prlz0ibUhUT3LFTuMI60HquXF96BNdNgePVd35EZVx4OAM0VKvYx/0MAjco3rfcjP6Wu28mJq8gIh30IxVZGs8=
Received: by 10.48.238.3 with SMTP id l3mr1525650nfh;
Thu, 08 Jun 2006 07:57:42 -0700 (PDT)
Received: by 10.48.231.12 with HTTP; Thu, 8 Jun 2006 07:57:42 -0700 (PDT)
Message-ID: <7be3f35d0606080757h3e5db37fqe3c1dd20663d4e7d@mail.gmail.com>
Date: Thu, 8 Jun 2006 16:57:42 +0200
From: "Harald Armin Massa" <haraldarminmassa@gmail.com>
To: pgsql-general <pgsql-general@postgresql.org>
Subject: Out of Memory Error on Postgresql 8.1.3. on win32
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_258_23266422.1149778662809"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200606/268
X-Sequence-Number: 96640
------=_Part_258_23266422.1149778662809
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Hello,
today postgresql 8.1.3 on win32 died:
2006-06-08 16:33:09 LOG: autovacuum: processing database "ibox"
TopMemoryContext: 84400 total in 7 blocks; 12696 free (22 chunks); 71704
used
Operator class cache: 8192 total in 1 blocks; 4936 free (0 chunks); 3256
used
TopTransactionContext: 8192 total in 1 blocks; 7552 free (10 chunks); 640
used
MessageContext: 8192 total in 1 blocks; 7368 free (1 chunks); 824 used
smgr relation table: 8192 total in 1 blocks; 3904 free (0 chunks); 4288 use=
d
Portal hash: 8192 total in 1 blocks; 3912 free (0 chunks); 4280 used
PortalMemory: 8192 total in 1 blocks; 8040 free (0 chunks); 152 used
PortalHeapMemory: 15360 total in 4 blocks; 15160 free (543 chunks); 200 use=
d
Vacuum: 8192 total in 1 blocks; 6600 free (0 chunks); 1592 used
Relcache by OID: 8192 total in 1 blocks; 3896 free (0 chunks); 4296 used
CacheMemoryContext: 253952 total in 5 blocks; 13264 free (2 chunks); 240688
used
pg_index_indrelid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632
used
pg_type_typname_nsp_index: 1024 total in 1 blocks; 328 free (0 chunks); 696
used
pg_type_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 used
pg_trigger_tgrelid_tgname_index: 1024 total in 1 blocks; 328 free (0
chunks); 696 used
pg_statistic_relid_att_index: 1024 total in 1 blocks; 328 free (0 chunks);
696 used
pg_auth_members_member_role_index: 1024 total in 1 blocks; 328 free (0
chunks); 696 used
pg_auth_members_role_member_index: 1024 total in 1 blocks; 328 free (0
chunks); 696 used
pg_rewrite_rel_rulename_index: 1024 total in 1 blocks; 328 free (0 chunks);
696 used
pg_proc_proname_args_nsp_index: 1024 total in 1 blocks; 256 free (0 chunks)=
;
768 used
pg_proc_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 used
pg_operator_oprname_l_r_n_index: 1024 total in 1 blocks; 192 free (0
chunks); 832 used
pg_operator_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 use=
d
pg_opclass_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 used
pg_opclass_am_name_nsp_index: 1024 total in 1 blocks; 256 free (0 chunks);
768 used
pg_namespace_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632
used
pg_namespace_nspname_index: 1024 total in 1 blocks; 392 free (0 chunks); 63=
2
used
pg_language_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 use=
d
pg_language_name_index: 1024 total in 1 blocks; 392 free (0 chunks); 632
used
pg_inherits_relid_seqno_index: 1024 total in 1 blocks; 328 free (0 chunks);
696 used
pg_index_indexrelid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632
used
pg_authid_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 used
pg_authid_rolname_index: 1024 total in 1 blocks; 392 free (0 chunks); 632
used
pg_database_datname_index: 1024 total in 1 blocks; 392 free (0 chunks); 632
used
pg_conversion_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632
used
pg_conversion_name_nsp_index: 1024 total in 1 blocks; 328 free (0 chunks);
696 used
pg_conversion_default_index: 1024 total in 1 blocks; 192 free (0 chunks);
832 used
pg_class_relname_nsp_index: 1024 total in 1 blocks; 328 free (0 chunks); 69=
6
used
pg_class_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 used
pg_cast_source_target_index: 1024 total in 1 blocks; 328 free (0 chunks);
696 used
pg_attribute_relid_attnum_index: 1024 total in 1 blocks; 328 free (0
chunks); 696 used
pg_attribute_relid_attnam_index: 1024 total in 1 blocks; 328 free (0
chunks); 696 used
pg_amproc_opc_proc_index: 1024 total in 1 blocks; 256 free (0 chunks); 768
used
pg_amop_opr_opc_index: 1024 total in 1 blocks; 328 free (0 chunks); 696 use=
d
pg_amop_opc_strat_index: 1024 total in 1 blocks; 256 free (0 chunks); 768
used
pg_aggregate_fnoid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632
used
MdSmgr: 8192 total in 1 blocks; 8032 free (0 chunks); 160 used
LockTable (locallock hash): 8192 total in 1 blocks; 3912 free (0 chunks);
4280 used
Timezones: 48408 total in 2 blocks; 5968 free (0 chunks); 42440 used
ErrorContext: 8192 total in 1 blocks; 8176 free (0 chunks); 16 used
2006-06-08 16:33:12 ERROR: out of memory
2006-06-08 16:33:12 DETAIL: Failed on request of size 16777212.
what scares me: up to the error there is allways "free", "free", "free"...
what is wrong?
Harald
--=20
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstra=DFe 202b
70197 Stuttgart
0173/9409607
-
on different matter:
did you ever dream of visiting CERN? The place where the antimatter for
exploding Vatican is created? To eat in cantinas
with the worlds highest propability to stand in queue with future or past
Nobel Prize Winners? To talk about Web 2.5 at the place where Web 0.1 up to
Web 1.0 were developed? register at www.europython.org!
------=_Part_258_23266422.1149778662809
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Hello,<br><br>today postgresql 8.1.3 on win32 died:<br><br>2006-06-08 16:33=
:09 LOG: autovacuum: processing database "ibox"<br>TopMemor=
yContext: 84400 total in 7 blocks; 12696 free (22 chunks); 71704 used<br>Op=
erator class cache: 8192 total in 1 blocks; 4936 free (0 chunks); 3256 used
<br>TopTransactionContext: 8192 total in 1 blocks; 7552 free (10 chunks); 6=
40 used<br>MessageContext: 8192 total in 1 blocks; 7368 free (1 chunks); 82=
4 used<br>smgr relation table: 8192 total in 1 blocks; 3904 free (0 chunks)=
; 4288 used
<br>Portal hash: 8192 total in 1 blocks; 3912 free (0 chunks); 4280 used<br=
PortalMemory: 8192 total in 1 blocks; 8040 free (0 chunks); 152 used<br>Po=
rtalHeapMemory: 15360 total in 4 blocks; 15160 free (543 chunks); 200 used
<br>Vacuum: 8192 total in 1 blocks; 6600 free (0 chunks); 1592 used<br>Relc=
ache by OID: 8192 total in 1 blocks; 3896 free (0 chunks); 4296 used<br>Cac=
heMemoryContext: 253952 total in 5 blocks; 13264 free (2 chunks); 240688 us=
ed
<br>pg_index_indrelid_index: 1024 total in 1 blocks; 392 free (0 chunks); 6=
32 used<br>pg_type_typname_nsp_index: 1024 total in 1 blocks; 328 free (0 c=
hunks); 696 used<br>pg_type_oid_index: 1024 total in 1 blocks; 392 free (0 =
chunks); 632 used
<br>pg_trigger_tgrelid_tgname_index: 1024 total in 1 blocks; 328 free (0 ch=
unks); 696 used<br>pg_statistic_relid_att_index: 1024 total in 1 blocks; 32=
8 free (0 chunks); 696 used<br>pg_auth_members_member_role_index: 1024 tota=
l in 1 blocks; 328 free (0 chunks); 696 used
<br>pg_auth_members_role_member_index: 1024 total in 1 blocks; 328 free (0 =
chunks); 696 used<br>pg_rewrite_rel_rulename_index: 1024 total in 1 blocks;=
328 free (0 chunks); 696 used<br>pg_proc_proname_args_nsp_index: 1024 tota=
l in 1 blocks; 256 free (0 chunks); 768 used
<br>pg_proc_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 use=
d<br>pg_operator_oprname_l_r_n_index: 1024 total in 1 blocks; 192 free (0 c=
hunks); 832 used<br>pg_operator_oid_index: 1024 total in 1 blocks; 392 free=
(0 chunks); 632 used
<br>pg_opclass_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 =
used<br>pg_opclass_am_name_nsp_index: 1024 total in 1 blocks; 256 free (0 c=
hunks); 768 used<br>pg_namespace_oid_index: 1024 total in 1 blocks; 392 fre=
e (0 chunks); 632 used
<br>pg_namespace_nspname_index: 1024 total in 1 blocks; 392 free (0 chunks)=
; 632 used<br>pg_language_oid_index: 1024 total in 1 blocks; 392 free (0 ch=
unks); 632 used<br>pg_language_name_index: 1024 total in 1 blocks; 392 free=
(0 chunks); 632 used
<br>pg_inherits_relid_seqno_index: 1024 total in 1 blocks; 328 free (0 chun=
ks); 696 used<br>pg_index_indexrelid_index: 1024 total in 1 blocks; 392 fre=
e (0 chunks); 632 used<br>pg_authid_oid_index: 1024 total in 1 blocks; 392 =
free (0 chunks); 632 used
<br>pg_authid_rolname_index: 1024 total in 1 blocks; 392 free (0 chunks); 6=
32 used<br>pg_database_datname_index: 1024 total in 1 blocks; 392 free (0 c=
hunks); 632 used<br>pg_conversion_oid_index: 1024 total in 1 blocks; 392 fr=
ee (0 chunks); 632 used
<br>pg_conversion_name_nsp_index: 1024 total in 1 blocks; 328 free (0 chunk=
s); 696 used<br>pg_conversion_default_index: 1024 total in 1 blocks; 192 fr=
ee (0 chunks); 832 used<br>pg_class_relname_nsp_index: 1024 total in 1 bloc=
ks; 328 free (0 chunks); 696 used
<br>pg_class_oid_index: 1024 total in 1 blocks; 392 free (0 chunks); 632 us=
ed<br>pg_cast_source_target_index: 1024 total in 1 blocks; 328 free (0 chun=
ks); 696 used<br>pg_attribute_relid_attnum_index: 1024 total in 1 blocks; 3=
28 free (0 chunks); 696 used
<br>pg_attribute_relid_attnam_index: 1024 total in 1 blocks; 328 free (0 ch=
unks); 696 used<br>pg_amproc_opc_proc_index: 1024 total in 1 blocks; 256 fr=
ee (0 chunks); 768 used<br>pg_amop_opr_opc_index: 1024 total in 1 blocks; 3=
28 free (0 chunks); 696 used
<br>pg_amop_opc_strat_index: 1024 total in 1 blocks; 256 free (0 chunks); 7=
68 used<br>pg_aggregate_fnoid_index: 1024 total in 1 blocks; 392 free (0 ch=
unks); 632 used<br>MdSmgr: 8192 total in 1 blocks; 8032 free (0 chunks); 16=
0 used
<br>LockTable (locallock hash): 8192 total in 1 blocks; 3912 free (0 chunks=
); 4280 used<br>Timezones: 48408 total in 2 blocks; 5968 free (0 chunks); 4=
2440 used<br>ErrorContext: 8192 total in 1 blocks; 8176 free (0 chunks); 16=
used
<br>2006-06-08 16:33:12 ERROR: out of memory<br>2006-06-08 16:33:12 D=
ETAIL: Failed on request of size 16777212.<br><br>what scares me: up =
to the error there is allways "free", "free", "fre=
e"...
<br><br>what is wrong?<br><br>Harald<br><br><br clear=3D"all"><br>-- <br>GH=
UM Harald Massa<br>persuadere et programmare<br>Harald Armin Massa<br>Reins=
burgstra=DFe 202b<br>70197 Stuttgart<br>0173/9409607<br>-<br>on different m=
atter:=20
<br>did you ever dream of visiting CERN? The place where the antimatter for=
exploding Vatican is created? To eat in cantinas<br>with the worlds highes=
t propability to stand in queue with future or past Nobel Prize Winners? To=
talk about Web=20
2.5 at the place where Web 0.1 up to Web 1.0 were developed? register at <a=
href=3D"http://www.europython.org">www.europython.org</a>!
------=_Part_258_23266422.1149778662809--
Sorry; I meant a password at the operating system level, not at the postgresql level.
On my Linux system, without an OS level password, the only way to log in (in Linux) to the postgres account is by su'ing from root, which seems more secure than having a password for the postgres account.
----- Original Message -----
From: "jqpx37" <jqpx37@iprive.com>
To: pgsql-general@postgresql.org
Sent: Thursday, June 08, 2006 11:05 AM
Subject: [GENERAL] Password for postgresql superuser?
Is there any security risk in the postgresql superuser having a password?
I installed a Linux distro recently and had it install Postgresql. It automatically set up the postgres account; the account was set up with no password.
I could of course create a password, but it's not clear to me that's a good thing from a security standpoint.
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
From pgsql-general-owner@postgresql.org Thu Jun 8 12:44:44 2006
X-Original-To: pgsql-general-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
by postgresql.org (Postfix) with ESMTP id 457A89FA621
for <pgsql-general-postgresql.org@postgresql.org>; Thu, 8 Jun 2006 12:44:44 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
with ESMTP id 71388-01 for <pgsql-general-postgresql.org@postgresql.org>;
Thu, 8 Jun 2006 12:44:36 -0300 (ADT)
X-Greylist: delayed 00:19:59.849665 by SQLgrey-
Received: from poczta.homelinux.com (dqk136.neoplus.adsl.tpnet.pl [83.24.170.136])
by postgresql.org (Postfix) with ESMTP id 38EC59FA5C8
for <pgsql-general@postgresql.org>; Thu, 8 Jun 2006 12:44:36 -0300 (ADT)
Received: from rafal by poczta.homelinux.com with local (Exim 4.62)
(envelope-from <rafal@zorro.isa-geek.com>)
id 1FoMN6-0005k0-5j; Thu, 08 Jun 2006 17:24:32 +0200
Subject: Re: Password for postgresql superuser?
From: Rafal Pietrak <rafal@zorro.isa-geek.com>
To: jqpx37@iprive.com
Cc: pgsql-general@postgresql.org
In-Reply-To: <20060608150832.9B6846400B5@iprive.iconicnetworks.com>
References: <20060608140554.35A6C640060@iprive.iconicnetworks.com>
<20060608150832.9B6846400B5@iprive.iconicnetworks.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Thu, 08 Jun 2006 17:24:30 +0200
Message-Id: <1149780271.22835.207.camel@model.home.waw.pl>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: rafal@zorro.isa-geek.com
X-SA-Exim-Scanned: No (on poczta.homelinux.com); SAEximRunCond expanded to false
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200606/270
X-Sequence-Number: 96642
On Thu, 2006-06-08 at 09:08 -0600, jqpx37 wrote:
Sorry; I meant a password at the operating system level, not at the postgresql level.
On my Linux system, without an OS level password, the only way to log in (in Linux) to the postgres account is by su'ing from root, which seems more secure than having a password for the postgres account.
Have you tried sudo ("sudo" command)?
It asks for a personal password, and grants whatever priviledge is
configured for that person, even root priviledge.
-R
----- Original Message -----
From: "jqpx37" <jqpx37@iprive.com>
To: pgsql-general@postgresql.org
Sent: Thursday, June 08, 2006 11:05 AM
Subject: [GENERAL] Password for postgresql superuser?Is there any security risk in the postgresql superuser having a password?
I installed a Linux distro recently and had it install Postgresql. It automatically set up the postgres account; the account was set up with no password.
I could of course create a password, but it's not clear to me that's a good thing from a security standpoint.
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?http://www.postgresql.org/docs/faq
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
--
-R
jqpx37@iprive.com ("jqpx37") writes:
Is there any security risk in the postgresql superuser having a
password?I installed a Linux distro recently and had it install Postgresql.
It automatically set up the postgres account; the account was set up
with no password.I could of course create a password, but it's not clear to me that's
a good thing from a security standpoint.
That depends on your security policies.
There's a pretty good argument to be made that a 'postgres' account
should only permit people in via "su -", in which case it might not
need to have an individual password...
--
(format nil "~S@~S" "cbbrowne" "cbbrowne.com")
http://www3.sympatico.ca/cbbrowne/oses.html
"If you give someone Fortran, he has Fortran.
If you give someone Lisp, he has any language he pleases."
-- Guy L. Steele Jr.
----- Original Message -----
From: "Chris Browne" <cbbrowne@acm.org>
To: pgsql-general@postgresql.org
Sent: Thursday, June 08, 2006 01:30 PM
Subject: [GENERAL] Password for postgresql superuser?
jqpx37@iprive.com ("jqpx37") writes:
Is there any security risk in the postgresql superuser having a
password?I installed a Linux distro recently and had it install Postgresql.
It automatically set up the postgres account; the account was set up
with no password.I could of course create a password, but it's not clear to me that's
a good thing from a security standpoint.That depends on your security policies.
There's a pretty good argument to be made that a 'postgres' account
should only permit people in via "su -", in which case it might not
need to have an individual password...
Thanks for your response.
I found allusions to the point your making, though no detailed explanation. It makes sense even without a thorough explication.
Best wishes
--
(format nil "~S@~S" "cbbrowne" "cbbrowne.com")
http://www3.sympatico.ca/cbbrowne/oses.html
"If you give someone Fortran, he has Fortran.
If you give someone Lisp, he has any language he pleases."
-- Guy L. Steele Jr.---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?http://www.postgresql.org/docs/faq
From pgsql-general-owner@postgresql.org Tue Jun 13 10:39:59 2006
X-Original-To: pgsql-general-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
by postgresql.org (Postfix) with ESMTP id 03F309FA5BE
for <pgsql-general-postgresql.org@postgresql.org>; Tue, 13 Jun 2006 10:39:59 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
with ESMTP id 78464-04 for <pgsql-general-postgresql.org@postgresql.org>;
Tue, 13 Jun 2006 10:39:55 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from iprive.iconicnetworks.com (c2.3c.5d45.static.theplanet.com [69.93.60.194])
by postgresql.org (Postfix) with ESMTP id 9D2609FA12F
for <pgsql-general@postgresql.org>; Tue, 13 Jun 2006 10:39:55 -0300 (ADT)
Received: by iprive.iconicnetworks.com (Postfix, from userid 48)
id 56CF5640027; Tue, 13 Jun 2006 07:39:54 -0600 (MDT)
To: pgsql-general@postgresql.org
Subject: PostgreSQL and Apache
Reply-To: <jqpx37@iprive.com>
From: "jqpx37" <jqpx37@iprive.com>
MIME-Version: 1.0
X-Mailer: HiveMail 1.2.1
Date: Tue, 13 Jun 2006 07:39:54 -0600
X-Priority: 3
Message-Id: <20060613133954.56CF5640027@iprive.iconicnetworks.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200606/508
X-Sequence-Number: 96880
I'm working on a project involving PostgreSQL and Apache.
Anyone know of any good books or online how-to's on getting PostgreSQL and Apache to work together? (I'm also using PHP.)
TIA
From pgsql-general-owner@postgresql.org Tue Jun 13 10:45:52 2006
X-Original-To: pgsql-general-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
by postgresql.org (Postfix) with ESMTP id 7220C9FA5BE
for <pgsql-general-postgresql.org@postgresql.org>; Tue, 13 Jun 2006 10:45:52 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
with ESMTP id 78716-09 for <pgsql-general-postgresql.org@postgresql.org>;
Tue, 13 Jun 2006 10:45:44 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178])
by postgresql.org (Postfix) with ESMTP id E9E829FA12F
for <pgsql-general@postgresql.org>; Tue, 13 Jun 2006 10:45:43 -0300 (ADT)
Received: by py-out-1112.google.com with SMTP id b29so1768662pya
for <pgsql-general@postgresql.org>; Tue, 13 Jun 2006 06:45:41 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:mime-version:content-type;
b=TkC5brEBeY8/lCg9ZsYqBA/v/alji7KQsl4o8P1OdXwqEbsKuDVzbwkWTf3AUpDfVa1Q2ZfsNKNQSO9bzJIeUizznih44gTN3/aSJfzugkgbzlwg5+29PGPjZOAwIrDq5Rls4vsIkFZq0AoLFrhZF2EDmlBpm8c4ZPt8xKo2dMA=
Received: by 10.35.89.10 with SMTP id r10mr2844722pyl;
Tue, 13 Jun 2006 06:45:40 -0700 (PDT)
Received: by 10.35.117.13 with HTTP; Tue, 13 Jun 2006 06:45:40 -0700 (PDT)
Message-ID: <7e444d3e0606130645k47d66579kfeaf276130012731@mail.gmail.com>
Date: Tue, 13 Jun 2006 16:45:40 +0300
From: "andrey dmitrenko" <jan2ary@gmail.com>
To: pgsql-general@postgresql.org
Subject: Cant' create language - "could not load library"
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_13294_2118864.1150206340725"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200606/509
X-Sequence-Number: 96881
------=_Part_13294_2118864.1150206340725
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hello All.
I have installed version 8.1.4 (located in D:/PostgreSQL/8.1 ) on Windows XP
and try to create language with command CREATE LANGUAGE or createlang
command line tool but in any way got an error:
postgres=# create language plperl;
ERROR: could not load library "D:/PostgreSQL/8.1/lib/plperl.dll": The
specified module could not be found.
and the same for any language except of plpgsql.
Also I have tried to create language java from command line:
java org.postgresql.pljava.deploy.Deployer -install
but got the same error.
All of the dll-libraries are exist
in dynamic_library_path, and on their places.
I've read thread
http://archives.postgresql.org/pgsql-bugs/2006-03/msg00039.php and some
referenced but got nothing.
Is this real bug or it's possible to resolve it and how?
Thanks.
------=_Part_13294_2118864.1150206340725
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hello All.<br><br>I have installed version 8.1.4 (located in D:/PostgreSQL/8.1 ) on Windows XP and try to create language with command CREATE LANGUAGE or createlang command line tool but in any way got an error:<br><br>postgres=# create language plperl;
<br>ERROR: could not load library "D:/PostgreSQL/8.1/lib/plperl.dll": The specified module could not be found.<br><br>and the same for any language except of plpgsql.<br>Also I have tried to create language java from command line:
<br><br>java org.postgresql.pljava.deploy.Deployer -install<br><br>but got the same error.<br>All of the dll-libraries are exist in dynamic_library_path, and on their places. <br> I've read thread <a href="http://archives.postgresql.org/pgsql-bugs/2006-03/msg00039.php">
http://archives.postgresql.org/pgsql-bugs/2006-03/msg00039.php</a> and some referenced but got nothing.<br><br>Is this real bug or it's possible to resolve it and how?<br> <br>Thanks.<br>
------=_Part_13294_2118864.1150206340725--