| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2012-01-18 01:56:46 | Re: Patch review for logging hooks (CF 2012-01) |
| Previous Message | Robert Haas | 2012-01-18 01:28:38 | Re: Should I implement DROP INDEX CONCURRENTLY? |