------=_Part_11528_23471032.1207820981644
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
the point i was trying to make is that pgAdmin seems to have the
possibility
to restore the connection, since opening a new sql window does the trick.
"All you'd need to do" would be to invoke this behavior when it is
necessary, without opening a new window.
cheers,
WBL
On Mon, Apr 7, 2008 at 6:18 PM, Willy-Bas Loos <willybas@[EMAIL PROTECTED]
> wrote:
>
> Hi,
>
> We also have issues with connections ending abrubtly. Not only with
> pgAdmin by the way.
> We're at the end of a DSL line, and the connection usually has a lot of
> hiccups.
> After one of those hiccups, you have to wait for at least 30 seconds to
> find out what happened, after which you get a correct error message, and
a
> dialog suggesting to close the server browser.
> Sometimes, not quite reproducable, pgAdmin will crash instead of showing
> the error message.
> During these 30 seconds, during which, presumably, pgAdmin waits for a
> server response, interaction with any of the pgAdmin windows is not
> possible, so that queries cannot be saved, nor can the request be
cancelled.
>
> It seems that the main window in pgAdmin is more sensitive to these
> hiccups than the SQL window. Sometimes (it's hard to say exactly when,
> because you can't notice the hiccups otherwise) the main window will not
> work anymore, whereas the SQL window will.
> You can trick pgAdmin to reconnect by pressing the "new" button in the
SQL
> window, the new window will have a connection (copy paste the query and
> close the stale window).
> But it would be MUCH nicer (these hiccups are driving us crazy) if
pgAdmin
> would be less sensitive. For example, reconnect when there is user
activity
> after connection is lost. Also, it would be nice if there would be the
> option to cancel the query once you notice that the connection has been
> lost, and the possibility to save your work in those 30-50 secs that
> sometimes feel like 30 minutes.
>
> Cheers, btw, i am a great pgAdmin fan.
>
> WBL
>
>
>
>
>
>
>
> On Tue, Apr 1, 2008 at 5:56 PM, Dave Page <dpage@[EMAIL PROTECTED]
> wrote:
>
> > On Mon, Mar 31, 2008 at 9:59 PM, Maciek Sakrejda
<msakrejda@[EMAIL PROTECTED]
>
> > wrote:
> > > I was able to reproduce this on 1.8.2, building from source (and I
get
> > > the hang this time, not the segfault). A small dialog box comes up
to
> > > tell me something (possibly that it's about to segfault), but it's
> > not
> > > drawn correctly (presumably because the refresh drawing routines
> > don't
> > > get called correctly by that point), so I'm not sure what it says.
> > Then
> > > pgAdmin stays like this until I try to close that dialog, at which
> > point
> > > I get the "Not responding/Wait/Force Quit" dialog box from Gnome.
> > >
> > > I noticed that I get the following on the command line where I
start
> > > pgadmin:
> > >
> > > Xlib: unexpected async reply (sequence 0xf810)!
> >
> > Can you get a backtrace? This might require you to build a debug
enabled
> > binary.
> >
> >
> > --
> > Dave Page
> > EnterpriseDB UK Ltd: http://www.enterprisedb.com
> > PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
> >
> > --
> > Sent via pgadmin-sup****t mailing list (pgadmin-sup****t@[EMAIL PROTECTED]
)
> > To make changes to your subscription:
> > http://www.postgresql.org/mailpref/pgadmin-sup****t
> >
>
>
------=_Part_11528_23471032.1207820981644
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
the point i was trying to make is that pgAdmin seems to have the
possibility to restore the connection, since opening a new sql window does
the trick. "All you'd need to do" would be to invoke this
behavior when it is necessary, without opening a new window. <br>
<br>cheers,<br><br>WBL<br><br><div class="gmail_quote">On Mon, Apr 7, 2008
at 6:18 PM, Willy-Bas Loos <<a
href="mailto:willybas@[EMAIL PROTECTED]
">willybas@[EMAIL PROTECTED]
>>
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Hi,<br><br>We also have issues with connections ending abrubtly. Not
only with pgAdmin by the way.<br>We're at the end of a DSL line, and
the connection usually has a lot of hiccups.<br>After one of those
hiccups, you have to wait for at least 30 seconds to find out what
happened, after which you get a correct error message, and a dialog
suggesting to close the server browser.<br>
Sometimes, not quite reproducable, pgAdmin will crash instead of showing
the error message.<br>During these 30 seconds, during which, presumably,
pgAdmin waits for a server response, interaction with any of the pgAdmin
windows is not possible, so that queries cannot be saved, nor can the
request be cancelled.<br>
<br>It seems that the main window in pgAdmin is more sensitive to these
hiccups than the SQL window. Sometimes (it's hard to say exactly when,
because you can't notice the hiccups otherwise) the main window will
not work anymore, whereas the SQL window will.<br>
You can trick pgAdmin to reconnect by pressing the "new" button
in the SQL window, the new window will have a connection (copy paste the
query and close the stale window).<br>But it would be MUCH nicer (these
hiccups are driving us crazy) if pgAdmin would be less sensitive. For
example, reconnect when there is user activity after connection is lost.
Also, it would be nice if there would be the option to cancel the query
once you notice that the connection has been lost, and the possibility to
save your work in those 30-50 secs that sometimes feel like 30
minutes.<br>
<br>Cheers, btw, i am a great pgAdmin fan.<br><font
color="#888888"><br>WBL</font><div><div></div><div
class="Wj3C7c"><br><br><br><br><br><br><br><div class="gmail_quote">On
Tue, Apr 1, 2008 at 5:56 PM, Dave Page <<a
href="mailto:dpage@[EMAIL PROTECTED]
" target="_blank">dpage@[EMAIL PROTECTED]
>>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204,
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>On Mon, Mar
31, 2008 at 9:59 PM, Maciek Sakrejda <<a
href="mailto:msakrejda@[EMAIL PROTECTED]
"
target="_blank">msakrejda@[EMAIL PROTECTED]
>> wrote:<br>
> I was able to reproduce this on 1.8.2, building from source (and I
get<br>
> the hang this time, not the segfault). A small dialog box comes
up to<br>
> tell me something (possibly that it's about to segfault),
but it's not<br>
> drawn correctly (presumably because the refresh drawing
routines don't<br>
> get called correctly by that point), so I'm not sure what
it says. Then<br>
> pgAdmin stays like this until I try to close that dialog, at
which point<br>
> I get the "Not responding/Wait/Force Quit" dialog box
from Gnome.<br>
><br>
> I noticed that I get the following on the command line where I
start<br>
> pgadmin:<br>
><br>
> Xlib: unexpected async reply (sequence 0xf810)!<br>
<br>
</div>Can you get a backtrace? This might require you to build a debug
enabled binary.<br>
<div><br>
<br>
--<br>
Dave Page<br>
EnterpriseDB UK Ltd: <a href="http://www.enterprisedb.com"
target="_blank">http://www.enterprisedb.com</a><br>
PostgreSQL UK 2008 Conference: <a href="http://www.postgresql.org.uk"
target="_blank">http://www.postgresql.org.uk</a><br>
<br>
--<br>
</div><div><div></div><div>Sent via pgadmin-sup****t mailing list (<a
href="mailto:pgadmin-sup****t@[EMAIL PROTECTED]
"
target="_blank">pgadmin-sup****t@[EMAIL PROTECTED]
>)<br>
To make changes to your subscription:<br>
<a href="http://www.postgresql.org/mailpref/pgadmin-sup****t"
target="_blank">http://www.postgresql.org/mailpref/pgadmin-sup****t</a><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>
------=_Part_11528_23471032.1207820981644--
|
