Re: \watch stuck on execution of commands returning no tuples - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: \watch stuck on execution of commands returning no tuples
Date
Msg-id CAB7nPqTcR+9U+mJUkVTrKBZp-P+qyo=iE-93-uYYa5LHeTx0Pg@mail.gmail.com
Whole thread Raw
In response to Re: \watch stuck on execution of commands returning no tuples  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: \watch stuck on execution of commands returning no tuples  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers



On Thu, May 2, 2013 at 11:01 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Michael Paquier <michael.paquier@gmail.com> writes:
> 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

It's not "waiting", it's doing the ANALYZE once every ten seconds,
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
$TAG

Regards,
--
Michael

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Recovery target 'immediate'
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] pgbench --throttle (submission 4)