Re: [pgadmin-support] Keep-alive?

2003-10-09 Thread Dave Page
 

> -Original Message-
> From: Adam H.Pendleton [mailto:[EMAIL PROTECTED] 
> Sent: 09 October 2003 03:25
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] Keep-alive?
> 
> 
> On Wednesday, Oct 8, 2003, at 07:27 US/Eastern, 
> [EMAIL PROTECTED] wrote:
> 
> > I think that adding an option to PgAdmin "send keepalive packages 
> > every <##> seconds" would be a valuable addition...
> >
> 
> I think this would be a much more viable solution than 
> re-connecting to 
> the database.

No network level solution is viable for us unless we want to maintain
our own replacement for libpq, besides which, even if we did implement
some kind of icmp heartbeat, there's no guarantee it would help because
it would be completely independent from any TCP connections - a firewall
might still decide to close what it thinks are idle connections inspite
of icmp messages.

Istm that there are 2 options:

1) Implement reconnects in pgConn.cpp. The major objection to this is
that the server may not notice that the original connection is dead, and
thus a number of dead connections may build up until the connection
limit on the server is reached. I think this problem is actually a bit
irrelevant - as things stand at the moment, if you connection drops, you
manually reconnect as soon as you need to. How many of us ever go and
look for dead connections on the server, and even if you did, and found
some, what would you do about it short of restarting the server?

2) Implement SQL level keep alives. This could a be simple SELECT
version() query that is executed automatically after n seconds of
inactivity.

Thoughts?

Regards, Dave.

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org


Re: [pgadmin-support] Keep-alive?

2003-10-09 Thread Adam H. Pendleton
Dave Page wrote:

2) Implement SQL level keep alives. This could a be simple SELECT
version() query that is executed automatically after n seconds of
inactivity.
 

This is what I had in mind, an application (i.e., layer 7) level keep-alive.

ahp

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
 subscribe-nomail command to [EMAIL PROTECTED] so that your
 message can get through to the mailing list cleanly


Re: [pgadmin-support] Keep-alive?

2003-10-09 Thread Dave Page
 

> -Original Message-
> From: Adam H. Pendleton [mailto:[EMAIL PROTECTED] 
> Sent: 09 October 2003 13:31
> To: Dave Page
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 
> [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] Keep-alive?
> 
> Dave Page wrote:
> 
> >2) Implement SQL level keep alives. This could a be simple SELECT
> >version() query that is executed automatically after n seconds of 
> >inactivity.
> >
> >  
> >
> This is what I had in mind, an application (i.e., layer 7) 
> level keep-alive.

OK, just fiddling around here - attached is a patch that implements a
heartbeat on the master connection to each server. Currently it beats
every 5 seconds, though this would be made configurable/disable-able.

It doesn't actually do much other than throw an error message if it gets
an unexpected response.

Thoughts, comments?

Regards, Dave.


Heartbeat.patch
Description: Heartbeat.patch

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


[pgadmin-support] Cannot compile

2003-10-09 Thread Troels Arvin
Hello,

For a week, I've been trying to compile the CVS-version of pgadmin3 -
without luck. First, I tried with the wxWindows-RPMS from the ftp-site.
Now I'm trying with a wxWindows installation compiled from the latest
wxWindows CVS repository. Still no luck.

The error messages that I get are rather lengthy, so I've put them here:
http://troels.arvin.dk/misc/log-make.txt

My pgadmin3 configure-expression:
--with-wx=/usr/local/wxWindows --enable-debug
--prefix=/usr/local/pgadmin3/

My system: Red Hat Linux 9.0.

-- 
Greetings from Troels Arvin, Copenhagen, Denmark


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html