Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has)
| От | Maciek Sakrejda |
|---|---|
| Тема | Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has) |
| Дата | |
| Msg-id | CAOtHd0B8+FHsNKVGy8Bg39MX31eg2UpTUd1NxexZgVvOs-WUaA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has) (Nikolay Samokhvalov <samokhvalov@gmail.com>) |
| Ответы |
Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has)
Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has) Proposal: :SQL_EXEC_TIME (like :ROW_COUNT) Variable (psql) |
| Список | pgsql-hackers |
On Thu, Feb 23, 2023, 09:55 Nikolay Samokhvalov <samokhvalov@gmail.com> wrote:
On Thu, Feb 23, 2023 at 9:05 AM Maciek Sakrejda <m.sakrejda@gmail.com> wrote:I think Heikki's solution is probably more practical since (1) ..Note that these ideas target two *different* problems:- what was the duration of the last query- when was the last query executedSo, having both solved would be ideal.
Fair point, but since the duration solution needs to capture two timestamps anyway, it could print start time as well as duration.
The prompt timestamp could still be handy for more intricate session forensics, but I don't know if that's a common-enough use case.
Thanks,
Maciek
В списке pgsql-hackers по дате отправления: