On Thu, Apr 27, 2017 at 6:18 AM, basti wrote:
> Hallo, we have a Postgres database Server and around that there are 8
> clients get data from it.
>
> All servers are the the same datacenter i think (traceroute only 4-5 hops)
>
> Now we plan to move the server to an other hoster/datacenter.
>
> I h
Hallo, we have a Postgres database Server and around that there are 8
clients get data from it.
All servers are the the same datacenter i think (traceroute only 4-5 hops)
Now we plan to move the server to an other hoster/datacenter.
I have done simple test with ping and traceroute.
Is there a wa
El 07/08/15 a las 07:31, Ramesh T escribió:
> FATAL: syntax error in file "recovery.conf" line 2, near token "config"
> < 2015-08-07 05:21:13.086 EDT >LOG: startup process (PID 6129) exited with
> exit code 1
> < 2015-08-07 05:21:13.086 EDT >LOG: aborting startup due to startup
> process failure
On 8/6/2015 6:21 AM, Ramesh T wrote:
Hi all,
I got a problem when i start postgres server.
like'
could not connect to the server: connection refused on host
2.3.421.1 and accepting tcp/ip connection on port 5432.
any help appreciated..
you could start with telling us what ope
FATAL: syntax error in file "recovery.conf" line 2, near token "config"
< 2015-08-07 05:21:13.086 EDT >LOG: startup process (PID 6129) exited with
exit code 1
< 2015-08-07 05:21:13.086 EDT >LOG: aborting startup due to startup
process failure
in pg_log
I changed in Recovery.conf
restore_comm
any help
On Thu, Aug 6, 2015 at 6:51 PM, Ramesh T
wrote:
> Hi all,
> I got a problem when i start postgres server.
> like'
>could not connect to the server: connection refused on host
> 2.3.421.1 and accepting tcp/ip connection on port 5432.
>
> any help appreciated..
>
Hi all,
I got a problem when i start postgres server.
like'
could not connect to the server: connection refused on host
2.3.421.1 and accepting tcp/ip connection on port 5432.
any help appreciated..
On 04 Apr 2014, at 16:09 , Tom Lane wrote:
> Your log extract looks like the server side thought it got a connection
> closure command. In particular, the server process seems to have exited
> normally, and it did not write "LOG: unexpected EOF on client connection",
> which it would have done
Mark van Cuijk writes:
> Im developing an application using Postgres and when doing a transaction
> with a bunch of INSERT statements, the connection to the server (on
> localhost) often suddenly dies. Trying to diagnose the problem, Ive
> increased log levels and Ive run a tcpdump session t
Hi,
I’m developing an application using Postgres and when doing a transaction with
a bunch of INSERT statements, the connection to the server (on localhost) often
suddenly dies. Trying to diagnose the problem, I’ve increased log levels and
I’ve run a tcpdump session to find out what’s going on,
>
> Most of the cases we've seen like that have been because multiple
> threads in the client application were trying to use the same PGconn
> connection object concurrently. There's no cross-thread synchronization
> built into libpq, so you have to provide the interlocks yourself if
> there's any
Tim Uckun writes:
> I have lots of ruby daemons running connected to postgres. Some of
> them start getting connection errors after about a day or two of
> running. The odd thing is that they don't all get the same error.
> Some get this error: PGError: lost synchronization with server: got
> me
Hello.
I have lots of ruby daemons running connected to postgres. Some of
them start getting connection errors after about a day or two of
running. The odd thing is that they don't all get the same error.
Some get this error: PGError: lost synchronization with server: got
message type "T"
Others
Dan Joo wrote:
db=pg.connect('aqdev','localhost',5432,None,None,'postgres',None)
From the commandline the connection works great, but from a
cgi-script it barfs with the following message:
*InternalError*: could not create socket: Permission denied
My (obvious, granted) guess is that you're r
Just solved it.
For others, here is the solution.
setsebool -P httpd_can_network_connect_db 1
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Joo
Sent: Thursday, June 05, 2008 4:18 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] postgres connection problem
Hi all,
I have a problem connecting to postgres via the python pg module ONLY
from the cgi-scripts.
The command is:
db=pg.connect('aqdev','localhost',5432,None,None,'postgres',None)
>From the commandline the connection works great, but from a cgi-script
it barfs with the following m
On 3/18/08, Vernon Van Zandt <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> I keep getting the following error when attempting to establish a
> connection (from Perl):
>
> install_driver(Pg) failed: DBD::Pg object version undef does not match
> bootstrap parameter 2.2.2 at /usr/lib/perl/5.8/DynaLo
Greetings,
I keep getting the following error when attempting to establish a
connection (from Perl):
install_driver(Pg) failed: DBD::Pg object version undef does not match
bootstrap parameter 2.2.2 at /usr/lib/perl/5.8/DynaLoader.pm line 245.
Here's the body of code used to connect:
sub db_
Hi,
Can you tell me how the Postmaster communicates with postgres database
functions like Createdb, Destroydb, and createuser etc..
As i am trying to establish a connection betn postmaster & postgres but
everytime
following message is coming
createdb: not found
destroydb:not found
FATAL: Stream
19 matches
Mail list logo