John P Weatherman wrote:
It would also be helpful to know what your LD_LIBRARY_PATH looks like
and if you can do a 'find / -name libpq.so -print' to see where all the
copies of this library may reside.
Yeap, it's a fine place for it.
Sorry for the quick post but I was rushing d
Joshua D. Drake wrote:
On Thu, 2009-09-17 at 12:06 -0600, u235sentinel wrote:
This doesn't answer your question but why not use prepackaged binaries?
We're using prepackaged binaries from postgres.org and it seem to be
core dumping or seg faulting... well.. at least psql is. It d
It would also be helpful to know what your LD_LIBRARY_PATH looks like
and if you can do a 'find / -name libpq.so -print' to see where all the
copies of this library may reside.
On Thu, 2009-09-17 at 12:16 -0600, Scott Marlowe wrote:
> On Thu, Sep 17, 2009 at 12:06 PM, u235sentinel wrote:
> > No
On Thu, Sep 17, 2009 at 12:06 PM, u235sentinel wrote:
> Not sure if this is the right list but here goes.
>
> I have gnu gcc and make on a Solaris 10 AMD64 system and having a bit of a
> problem compling postgres 8.3.7 with openssl. I've even tried with a newly
> compiled version of openssl. Ver
On Thu, 2009-09-17 at 12:06 -0600, u235sentinel wrote:
> Not sure if this is the right list but here goes.
>
> I have gnu gcc and make on a Solaris 10 AMD64 system and having a bit of
> a problem compling postgres 8.3.7 with openssl. I've even tried with a
> newly compiled version of openssl.
Not sure if this is the right list but here goes.
I have gnu gcc and make on a Solaris 10 AMD64 system and having a bit of
a problem compling postgres 8.3.7 with openssl. I've even tried with a
newly compiled version of openssl. Verison 98 h-k.
I did read the solaris faq and it hasn't helpe
"Paul B. Anderson" writes:
> To clarify what a plain "vacuum" is, if you have an initdb data area,
> and the database listening on port ,
> Is this sufficient,
> export PGDATA=
> export PGPORT=
> vacuumdb --all --analyze
> running as user postgres (on Linux)?
The --analyze isn't really
To clarify what a plain "vacuum" is, if you have an initdb data area,
and the database listening on port ,
Is this sufficient,
export PGDATA=
export PGPORT=
vacuumdb --all --analyze
running as user postgres (on Linux)?
Thanks.
Paul Anderson
Tom Lane wrote:
Nigel Metheringham writes:
Scott Marlowe wrote:
> On Tue, Sep 15, 2009 at 3:58 AM, std pik wrote:
>> Hello all..
>> I'm using PostgreSQL 8.3..
>> How can I get information about the hardware utilization:
>> - CPU usage.
>> - Disk space.
>> - Memory allocation.
>> thank you.
>
> Dude, there was a whole thr
Nigel Metheringham writes:
> On 17 Sep 2009, at 14:57, Tom Lane wrote:
>> The symptoms indicate pretty strongly that you forgot about vacuuming
>> the system catalogs. A plain "VACUUM" executed in every database, by
>> a superuser, is sufficient for this. Trying to be smart by vacuuming
>> only
On 17 Sep 2009, at 14:57, Tom Lane wrote:
The symptoms indicate pretty strongly that you forgot about vacuuming
the system catalogs. A plain "VACUUM" executed in every database, by
a superuser, is sufficient for this. Trying to be smart by vacuuming
only what you think needs vacuumed is not s
Nigel Metheringham writes:
> I have a database thats been running in production use since 2006 on a
> Centos 4.7 (originally an earlier 4 release, updated incrementally).
> The pg version is somewhat ancient as we have stuck with the system
> postgres - currently postgresql-7.4.19-1.el4_6.1
On Thu, Sep 17, 2009 at 11:53:10AM +0200, Johan Greyling wrote:
> I ahve PostgreSQL 8.3 installed, after I restart my pc, using the
> pgAdminIII it gives me connection...failed
>
> What can I do?
My first reaction would be to check whether the server is running
e.g. nmap localhost -p 5432
On my
Hi,
I have a database thats been running in production use since 2006 on a
Centos 4.7 (originally an earlier 4 release, updated incrementally).
The pg version is somewhat ancient as we have stuck with the system
postgres - currently postgresql-7.4.19-1.el4_6.1.
Yesterday it all fell apar
Hi
I ahve PostgreSQL 8.3 installed, after I restart my pc, using the
pgAdminIII it gives me connection...failed
What can I do?
Tahnx
--
Johan Greyling
0823076776
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/m
** Message copied to the 'pgadmin-support' list **
Dmitry.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
16 matches
Mail list logo
