Re: \watch stuck on execution of commands returning no tuples

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: \watch stuck on execution of commands returning no tuples
Date: 2013-05-04 20:42:20
Message-ID: 12427.1367700140@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Done that way, thanks for the suggestion.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2013-05-04 20:57:44 Re: erroneous restore into pg_catalog schema
Previous Message Tom Lane 2013-05-04 19:59:49 Re: erroneous restore into pg_catalog schema