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

Re: psql \timing vs failed statements

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql \timing vs failed statements
Date: 2012-01-18 01:30:44
Message-ID: CA+TgmobOCy0jAORFFHqnXnaBWgTR89VqyUTORR5Qb4NN=1NCcw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Jan 17, 2012 at 10:01 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> Right now, psql \timing output only gives output for successful
> queries. Is there any actual reason for this, or just a "it happened"?
>
> In particular,I just had a very long run of a CREATE UNIQUE INDEX fail
> pretty far in - and I would've really liked to have timing output for
> that one even though it failed.
>
> Thus - if I were to change psql to output timing on failed queries as
> well, will anybody object? ;)

I won't.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Fujii MasaoDate: 2012-01-18 01:56:46
Subject: Re: Patch review for logging hooks (CF 2012-01)
Previous:From: Robert HaasDate: 2012-01-18 01:28:38
Subject: Re: Should I implement DROP INDEX CONCURRENTLY?

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