Re: \watch stuck on execution of commands returning no tuples
От | Michael Paquier |
---|---|
Тема | Re: \watch stuck on execution of commands returning no tuples |
Дата | |
Msg-id | CAB7nPqTcR+9U+mJUkVTrKBZp-P+qyo=iE-93-uYYa5LHeTx0Pg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: \watch stuck on execution of commands returning no tuples (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: \watch stuck on execution of commands returning no tuples
|
Список | pgsql-hackers |
On Thu, May 2, 2013 at 11:01 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
MichaelMichael Paquier <michael.paquier@gmail.com> writes:It's not "waiting", it's doing the ANALYZE once every ten seconds,
> Hi all,
> When testing \watch, I noticed that process waits indefinitely when
> executing it with a DDL or a DML.
> For example:
> postgres=# CREATE TABLE aa (a int);
> postgres=# ANALYSE aa \watch 10
> -- Process waiting here
just like you told it to.
Perhaps it'd be a good idea to emit the command tag on receiving a
non-tuple-bearing result, just to make this more obvious.
Yes, the command tag would be a good idea, combined with the watch time
that other commands returning tuples have, giving something like that:
Watch every 2s Fri May 3 10:01:04 2013
that other commands returning tuples have, giving something like that:
Watch every 2s Fri May 3 10:01:04 2013
$TAG
Regards,
-- В списке pgsql-hackers по дате отправления: