> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 17 February 2004 17:42
> To: Markus Wollny
> Cc: Josh Endries; pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] connection dropping continued
> >I wouldn't call that malfunctioning,
> So call it ill-configured.
I would call it malfunctioning, it's deliberately breaking tcp/ip by the
sounds of it. You say it's to prevent DOS attacks, but isn't that
exactly what it's caused itself?
> >, a simple "select 1;" issued every 30 odd
> >seconds to all opened databases would be absolutely
> sufficient, I should
> >think. If that feature is off by default and can be switched on (and
> >maybe the interval adjusted according to needs), no one would be
> >bothered by it either.
I experimented with this following the last round of borked firewalls
and it's virtually impossible to do without screwing up pgAdmin
completely - there are all sorts of threading/concurrency problems that
would take a massive rewrite to sort out - something I'm not prepared to
do to work around a problem caused by a firewall that doesn't implement
> We can not and thus will not implement app level keep-alives.
> You can try to head over to pgsql-bugs or pgsql-hackers, to recommend
> implementing that in libpq, and you certainly will get the
> same answer:
> FIX THE FIREWALL!
Agreed, I'm certain that's the response you will get (I've seen it
pgadmin-support by date
|Next:||From: Andreas Pflug||Date: 2004-02-17 20:10:44|
|Subject: Re: connection dropping continued|
|Previous:||From: Matt Doggett||Date: 2004-02-17 19:02:08|
|Subject: Re: inserting new records without OIDs|