pgadmin or pgsql? query execution bug

From: Kevin Field <kev(at)brantaero(dot)com>
To: pgadmin-support(at)postgresql(dot)org
Subject: pgadmin or pgsql? query execution bug
Date: 2007-08-09 12:45:33
Message-ID: 46BB0C6D.1000600@brantaero.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

So this works fine in 1.6.3 (and psql), but in 1.8.0 beta's query window:

-- Executing query:
select now()

Total query runtime: 32 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 3766 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 12141 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 1938 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 15 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 2031 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 13032 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 1250 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 1000 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 219 ms.
1 rows retrieved.

-- Executing query:
select now()::time

Total query runtime: 16 ms.
1 rows retrieved.

The weird part is, it always returns the row right away like it should,
but most times also keeps executing forever, until I press F5 again. To
get it to stop, pressing repeatedly a few times seems to help.

Kev

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Kevin Field 2007-08-09 12:48:16 operators, types, etc....where'd they go?
Previous Message Daniel Mendes 2007-08-09 11:01:18 Using Quotation marks.