Skip site navigation (1) Skip section navigation (2)

[pgAdmin III] #244: Crash with the lock report

From: "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org>
To:
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: [pgAdmin III] #244: Crash with the lock report
Date: 2010-09-29 17:08:58
Message-ID: 056.dd1f08120fc811373e8b4984605a30b4@code.pgadmin.org (view raw or flat)
Thread:
Lists: pgadmin-hackers
#244: Crash with the lock report
-----------------------------+----------------------------------------------
 Reporter:  Little, Douglas  |       Owner:  gleu
     Type:  bug              |      Status:  new 
 Priority:  minor            |   Milestone:      
Component:  pgadmin          |     Version:  1.12
 Keywords:  serverstatus     |    Platform:  all 
-----------------------------+----------------------------------------------
 In the server status screen.   If in the LOCKS section,  I click on the
 user column header I get this error. All of the other columns seem to be
 working correctly. I do not  have superuser credentials.

-- 
Ticket URL: <http://code.pgadmin.org/trac/ticket/244>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

Responses

pgadmin-hackers by date

Next:From: pgAdmin TracDate: 2010-09-29 17:10:17
Subject: [pgAdmin III] #245: Erroneous log_statement query in frmStatus
Previous:From: Guillaume LelargeDate: 2010-09-29 16:55:40
Subject: pgAdmin III commit: Fix the double line number in the function props

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group