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
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
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
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
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 reestablish it, and PgAdmin
>> crashed when I ran the query 2
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 reestablish it, and PgAdmin
> crashed when I ran the query 2 more times.
>
> I had run a query that took about 10 minutes t
I am running the latest release for Windows (XP) -- 1.12.0 (Sep 17, 2010).
The SQL query window lost the connect, failed to reestablish it, and PgAdmin
crashed when I ran the query 2 more times.
I had run a query that took about 10 minutes to complete. It completed. Then
I stepped away for a while
I was able to connect to a different database after I got the error.
However, now I could not get PgAdmin to crash.
After the first error, I connected to a different database with no problem.
Then I ran the query again, and got a slightly different error. Subsequent
runs of the query got the same
I'll check this.
I was running the test as if you had meant the latter, so I attempted to
disconnect from one of the databases to attempt to answer the former
question.
I was running the SQL test in two databases. When I went to disconnect from
one of the databases, the browser asked me if I want
The former.
On Monday, July 26, 2010, Michael Shapiro wrote:
> What do you mean: Can I select a different database after I get the error; or
> do I get the error using a different database?
>
>
> On Mon, Jul 26, 2010 at 2:05 PM, Dave Page wrote:
> On Mon, Jul 26, 2010 at 8:03 PM, Michael Shapir
What do you mean: Can I select a different database after I get the error;
or do I get the error using a different database?
On Mon, Jul 26, 2010 at 2:05 PM, Dave Page wrote:
> On Mon, Jul 26, 2010 at 8:03 PM, Michael Shapiro
> wrote:
> > What happens is that the first time it does give an err
On Mon, Jul 26, 2010 at 8:03 PM, Michael Shapiro wrote:
> What happens is that the first time it does give an error. But the editor is
> not useable. If I rerun the query a couple times, it can crash.
I tried running the query a bunch of times. It errored, but didn't crash.
Can you select a diff
What happens is that the first time it does give an error. But the editor is
not useable. If I rerun the query a couple times, it can crash.
On Mon, Jul 26, 2010 at 1:58 PM, Dave Page wrote:
> On Mon, Jul 26, 2010 at 5:41 PM, Michael Shapiro
> wrote:
> > I tested 1/12 beta. It has exactly the
On Mon, Jul 26, 2010 at 5:41 PM, Michael Shapiro wrote:
> I tested 1/12 beta. It has exactly the same problem. When the SQL editor
> loses the connection, rerunning the query causes PgAdmin to crash.
I can't reproduce that - it errors cleanly for me (which is why I
didn't work on the Query Tool e
Le 26/07/2010 20:04, Michael Shapiro a écrit :
> The IIRC patch works.
> Any chance of the SQL editor getting such a patch?
>
Could be. But not for 1.12, as we are on beta. I added a ticket for this
(http://code.pgadmin.org/trac/ticket/216).
--
Guillaume
http://www.postgresql.fr
http://dalib
The IIRC patch works.
Any chance of the SQL editor getting such a patch?
On Mon, Jul 26, 2010 at 11:48 AM, Guillaume Lelarge
wrote:
> Le 26/07/2010 18:41, Michael Shapiro a écrit :
> > I tested 1/12 beta. It has exactly the same problem. When the SQL editor
> > loses the connection, rerunning the
Le 26/07/2010 18:41, Michael Shapiro a écrit :
> I tested 1/12 beta. It has exactly the same problem. When the SQL editor
> loses the connection, rerunning the query causes PgAdmin to crash.
>
The patch Dave applied for 1.12 is only for the browser IIRC. The SQL
editor would need another patch.
I tested 1/12 beta. It has exactly the same problem. When the SQL editor
loses the connection, rerunning the query causes PgAdmin to crash.
On Fri, Jul 23, 2010 at 4:03 PM, Guillaume Lelarge
wrote:
> Le 23/07/2010 22:57, Michael Shapiro a écrit :
> > The visualtour page seems to imply that this w
Le 23/07/2010 22:57, Michael Shapiro a écrit :
> The visualtour page seems to imply that this works with 9.0, but it doesn't
> say if it works with previous versions.
> Will the reconnect work with 8.x (eg, 8.1)?
>
I don't see how you get to that conclusion. 1.12 has 9.0 support, but
this patch s
The visualtour page seems to imply that this works with 9.0, but it doesn't
say if it works with previous versions.
Will the reconnect work with 8.x (eg, 8.1)?
On Fri, Jul 23, 2010 at 3:47 PM, Guillaume Lelarge
wrote:
> Le 23/07/2010 22:26, Michael Shapiro a écrit :
> > Do you have a sense of wha
Le 23/07/2010 22:26, Michael Shapiro a écrit :
> Do you have a sense of what the patch "fixed"?
Sure, it's on the browser. When pgAdmin detects a dead connection, it
asks the user if he wants to try to reconnect. See
http://www.pgadmin.org/visualtour12.php, there is a screenshot of the
dialog.
>
Le 23/07/2010 15:13, Michael Shapiro a écrit :
> I am using PgAdmin 1.10.2 on Windows XP. PgAdmin has crashed on me three
> times in the last two hours. This happens when it loses the connection to
> the database. The Object Browser reports a problem (I can't recall the exact
> message) and after I
I am using PgAdmin 1.10.2 on Windows XP. PgAdmin has crashed on me three
times in the last two hours. This happens when it loses the connection to
the database. The Object Browser reports a problem (I can't recall the exact
message) and after I click OK (for each message) PgAdmin crashes.
The connection to the database is dropped occasionally (as far as I can
tell, independently of internet connectivity issues). I have experienced
this quite a lot. I do not think it is PgAdmin that drops the connection.
Could be postgres itself is dropping the connection.
There have been a number
On Tue, Oct 13, 2009 at 6:59 PM, John wrote:
> Hi,
> I have a fellow assocate that uses pgAdmin3 remotely (he is in GA the DB is in
> CA). He insists that a "time out" is somewhere in pgAdmin. He loses
> connection often. It has happen while are talking on Skype, or not talking
> on Skype. It'
Le mardi 13 octobre 2009 à 19:59:04, John a écrit :
> Hi,
> I have a fellow assocate that uses pgAdmin3 remotely (he is in GA the DB is
> in CA). He insists that a "time out" is somewhere in pgAdmin. He loses
> connection often. It has happen while are talking on Skype, or not
> talking on Sk
Hi,
I have a fellow assocate that uses pgAdmin3 remotely (he is in GA the DB is in
CA). He insists that a "time out" is somewhere in pgAdmin. He loses
connection often. It has happen while are talking on Skype, or not talking
on Skype. It's also has happened while I was remotely connected.
27 matches
Mail list logo
