Hi!
We use postgreSQL 8.1.2 in Solaris 9 platform to maintain very important
business data. The postgresql DB was interrupted now:
> more postgresql-2007-03-05_210154.log
LOG: could not bind socket for statistics collector: Cannot assign requested
address
LOG: database system was inter
Hi,
I have a 7Go pgsql_tmp directory in my main tablespace which remains
even after a cluster restart.
Does anyone know how to clean up properly ? Can i just delete the
directory in the filesystem (with the cluster up or down ?) ?
The documentation says it should be handled automatically by the
c
"David Levy" <[EMAIL PROTECTED]> writes:
> I have a 7Go pgsql_tmp directory in my main tablespace which remains
> even after a cluster restart.
> Does anyone know how to clean up properly ? Can i just delete the
> directory in the filesystem (with the cluster up or down ?) ?
If the postmaster's no
dear list,
I know there are already hunderts of posts about pg_hba.conf, but still
after reading a few of them I still got troubles with this topic.
I've got a vpn server with a ststic ip address, java apps are supposed to
run there receiving data from a postgresql database.
The database is run
What address are you connecting to on your desktop computer? You should be
using localhost:5432 which putty will redirect to the server via the SSH
tunnel and the server will connect to PostgreSQL on your behalf.
~p
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED
hello phillip,
yes, the connection i defined in pgadmin uses localhost:5432.
Still, no success :(
2007/3/6, Phillip Smith <[EMAIL PROTECTED]>:
What address are you connecting to on your desktop computer? You should
be using localhost:5432 which putty will redirect to the server via the S
What address are you using for "server.ip.address"?
I believe this is the address you should put in your pg_hba.conf, not
127.0.0.1.
Then in PgAdmin, connect to localhost:5432.
You can always check your PostgreSQL logs and see what source address
the request is coming from.
Andy.
Moritz Bay
I know your problem (I think)
Your SSH forward you said is defined as:
Lserver.ip.address:5432
So the requests will be coming from your server's IP address via the eth0
interface. You need to change this to 127.0.0.1 to make it use the lo
interface, and then the requests will come from 127
"Roger Pan" <[EMAIL PROTECTED]> writes:
>We use postgreSQL 8.1.2 in Solaris 9 platform to maintain very =
> important business data.
If it's as important as all that, you should make more of an effort to
keep up-to-date with PG minor releases...
> PANIC: failed to re-find parent key in "156
