From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Kirk Wolak <wolakk(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Subject: | Re: psql tests hangs |
Date: | 2023-05-12 15:50:53 |
Message-ID: | 1429717.1683906653@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> pá 12. 5. 2023 v 15:26 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
>> Oh! AFAICS, we don't do any of those things, but I agree it seems like
>> a good idea. Can you confirm that if you unset PSQL_WATCH_PAGER then
>> the test passes for you?
> yes, I tested it now, and unset PSQL_WATCH_PAGER fixed this issue.
OK. So after looking at this a bit, the reason PAGER and PSQL_PAGER
don't cause us any problems in the test environment is that they are
not honored unless isatty(fileno(stdin)) && isatty(fileno(stdout)).
It seems to me that it's a bug that there is no such check before
using PSQL_WATCH_PAGER. Is there actually any defensible reason
for that?
I think we do need to clear out all three variables in
Cluster::interactive_psql. But our regular psql tests shouldn't
be at risk here.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2023-05-12 15:54:00 | Re: Adding SHOW CREATE TABLE |
Previous Message | Aleksander Alekseev | 2023-05-12 15:39:04 | [PATCH] Slight improvement of worker_spi.c example |