Re: pgsql: Add PSQL_WATCH_PAGER for psql's \watch command.

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Add PSQL_WATCH_PAGER for psql's \watch command.
Date: 2021-07-14 04:08:32
Message-ID: CA+hUKGK5k3BanY_jLObNGBrQ+KJV0f+EVPk2jePOA+eoWE=tnA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Jul 14, 2021 at 6:17 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Just how badly did you want to use sigwait here? I'm having
> considerable second thoughts about the value of that change
> versus the hoops we're going to have to jump through to use it.

I'm sure I could find another way if it comes to it. The original
proposal had a sleep(0.1) loop... I thought this was more elegant, but
obviously I didn't know about this portability problem and there are
surely other ways. (Searching for sigwait in the archives brings up
some fun discussion of other long forgotten dinosaurs that also had
this problem.)

> (I suppose a hacky solution might be to never define USE_SIGWAIT
> on Solaris.)

Yeah I was thinking about that. I've just got a shell on an illumos
VM and will try a couple of ideas out if I can remember how to drive
this thing... more soon.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2021-07-14 07:18:51 pgsql: Fix lack of message pluralization
Previous Message Amit Kapila 2021-07-14 02:41:43 pgsql: Add support for prepared transactions to built-in logical replic