From: | Joe Van Dyk <joe(at)tanga(dot)com> |
---|---|
To: | |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Analyzing last run query in psql |
Date: | 2013-07-03 21:58:13 |
Message-ID: | CACfv+pLrKe_J56=VmER8KvJOHW4WowJQgmr0FTa7Ls7Njz=C4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'd like the execution plan to be in the psql output, not in the postgres
log.
On Tue, Jul 2, 2013 at 11:20 PM, Andreas Kretschmer <
akretschmer(at)spamfence(dot)net> wrote:
> Joe Van Dyk <joe(at)tanga(dot)com> wrote:
>
> > I frequently need to analyze the last query in psql:
> > select * from table where id = 1;
> > explain analyze select * from table where id = 1;
> >
> > It would be nice to be able to do this:
> > explain analyze $LAST
> >
> > (or can I do something like that already?)
> >
> > I'm not using psql interactively, I pipe files into psql (if it matters).
>
> There is no history or something like that, but you can use autoexplain.
> http://www.postgresql.org/docs/9.2/interactive/auto-explain.html
>
>
>
>
> Andreas
> --
> Really, I'm not out to destroy Microsoft. That will just be a completely
> unintentional side effect. (Linus Torvalds)
> "If I was god, I would recompile penguin with --enable-fly." (unknown)
> Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Carville | 2013-07-03 22:17:32 | Re: Cannot connect to remote postgres database |
Previous Message | Joe Van Dyk | 2013-07-03 21:56:52 | Re: Analyzing last run query in psql |