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

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

On Sun, May 5, 2013 at 5:42 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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.
>
Thanks a lot for the fix.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2013-05-06 07:13:55 Re: 9.3 Beta1 status report
Previous Message Amit Kapila 2013-05-06 05:47:17 Re: Meaning of keyword category list in src/backend/parser/gram.y