Hello
I use 1.12.0 PGAdminIII from a client for seven windows connect to a
postgres server 8.4.2.1 installed on a Windows 2008 server 32-bit server
(service pack 2). The connection is extremely slow.
Should we change a parameter in the configuration either Postgres or
pgAdmin?
Thank you
MCQ
Le 27/09/2010 11:58, Marie-Claude QUIDOZ a écrit :
> Hello
>
> I use 1.12.0 PGAdminIII from a client for seven windows connect to a
> postgres server 8.4.2.1 installed on a Windows 2008 server 32-bit server
> (service pack 2). The connection is extremely slow.
>
> Should we change a parameter in
On Sat, Sep 25, 2010 at 8:32 AM, Dave Page wrote:
> On Sat, Sep 25, 2010 at 8:22 AM, Guillaume Lelarge
> wrote:
>> Le 24/09/2010 18:17, Michael Shapiro a écrit :
>>> I am running the latest release for Windows (XP) -- 1.12.0 (Sep 17, 2010).
>>> The SQL query window lost the connect, failed to ree
It is frustrating, it is not reproducible by me either. I can't find a way
to force it happen. I even had the sys-admins on the server kill the backend
process that was connected to the query window and could not get the crash.
I have had my system checked to see if there are hardware issues that
Hello
I find a solution
If I put the IP number (x.x.x.x) instead of the name of the server, the
connection is speed.
Thanks
MCQ
-Message d'origine-
De : Marie-Claude QUIDOZ
Envoyé : lundi 27 septembre 2010 15:32
À : Guillaume Lelarge
Cc : pgadmin-support@postgresql.org
Objet : RE: [p
Le 27/09/2010 17:47, Marie-Claude QUIDOZ a écrit :
> [...]
> I find a solution
>
> If I put the IP number (x.x.x.x) instead of the name of the server, the
> connection is speed.
>
Which means you have a DNS resolution issue, not a PostgreSQL or pgAdmin
issue.
You should probably talk to your s
Le 27/09/2010 17:27, Michael Shapiro a écrit :
> It is frustrating, it is not reproducible by me either. I can't find a way
> to force it happen. I even had the sys-admins on the server kill the backend
> process that was connected to the query window and could not get the crash.
>
> I have had my
OK. I'll live with it. I know what happens. I run query once. Then I let the
window sit idle for a while (long enough for the connection to get dropped,
or at least I think it is dropped). Then I re-run the query. I get an error
message (but no prompt to reconnect). Then if I run the query yet agai
