On Wed, 2003-02-12 at 00:09, Sebastian Muench wrote:
> Hi all,
>
> we builded a pqsql 7.3.2 (with perl support) at our redhat 8.0.
> We builded libperl.so. Now we are trying to execute
>
> createlang plperl "ourdatabase".
>
> We are getting the message:
>
> ERROR: stat failed on file '$
Robert Treat <[EMAIL PROTECTED]> writes:
> On Tue, 2003-02-11 at 17:27, Patrick S. Riedel wrote:
>> I have a client with a v7.0.2-2c1 database stored on media. The
>> database files were stored raw, not dumped. Their current pgsql version
>> is 7.1; they do not have v7.0.2-2c1 installed anywhere.
On Tue, 11 Feb 2003, Vicki Brown wrote:
> Does this test failure "matter"?
> This is a new installation of PostgreSQL 7.3.2 on FreeBSD 4.7
It looks like a -0 vs 0 difference, so not really.
---(end of broadcast)---
TIP 5: Have you checked our ext
Does this test failure "matter"?
This is a new installation of PostgreSQL 7.3.2 on FreeBSD 4.7
...
test geometry ... FAILED
...
more src/test/regress/regression.diffs
*** ./expected/geometry-bsd-precision.out Mon Oct 28 19:44:22 2002
--- ./results/geometry.out Tue Feb 11 19
Hi all,
we builded a pqsql 7.3.2 (with perl support) at our redhat 8.0.
We builded libperl.so. Now we are trying to execute
createlang plperl "ourdatabase".
We are getting the message:
ERROR: stat failed on file '$libdir/plperl': No such file or directory.
Can anyone of you explain us, w
I'm just following up on my begging last Friday re PAM and PostgreSQL
from ... with more begging. As I mentioned last time, I've seen this
problem mentioned before but have never seen it solved. Is there simply
no solution? Is there some obvious, stupid mistake I'm making? Has
anyone out there actu
On Tue, 2003-02-11 at 17:27, Patrick S. Riedel wrote:
> I have a client with a v7.0.2-2c1 database stored on media. The
> database files were stored raw, not dumped. Their current pgsql version
> is 7.1; they do not have v7.0.2-2c1 installed anywhere.
>
> Can I update/add their old db into their
I have a client with a v7.0.2-2c1 database stored on media. The
database files were stored raw, not dumped. Their current pgsql version
is 7.1; they do not have v7.0.2-2c1 installed anywhere.
Can I update/add their old db into their new system without installing
v7.0.2-2c1 onto another system to
Server won't shutdown:
Currently, we are running 7.3.2. However, we have had this problem since 7.1.
Our production server has dozens of connections from different persistent
applications (some web, some runnning on other systems).
When I do a shutdown:
$pgpath/bin/pg_ctl -D $datadir -m fast
Thanks. That did the trick. I knew there had to be a simple solution.
At 04:14 PM 2/11/03 +0800, you wrote:
>
> Mike,
> Have you tried adding an entry for the entire Internet?
> eg: IP: 127.0.0.1(could be anything) Mask: 0.0.0.0
>
> Mike.(also)
>
> > -Original Message-
> > From: Mik
I've reads from other milist(Mr.Aris
Wendy),
And he was asking about How to Configuring
the PostgreSQL and spread the database to
different hardisk. And I thought he has
succesfully spread the database to
another
physical disk.
And I wonder Now. Could I spread the
Schema to ??, Was i
I'm setting up a staging / test installation of a running application, and
have copied the PG data directory (/var/pgsql/data) to the new machine via a
tarball and replaced the data directory created with the initdb run when PG
was installed on the new server.
Is anything special required to get a
Title: RE: [ADMIN] ODBC and unknown i.p.
Mike,
Have you tried adding an entry for the entire Internet?
eg: IP: 127.0.0.1(could be anything) Mask: 0.0.0.0
Mike.(also)
> -Original Message-
> From: Mike Alford [mailto:[EMAIL PROTECTED]]
> Sent: Monday, 10 February 2003 9:44 PM
> To: [
13 matches
Mail list logo
