From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Will Leinweber <will(at)heroku(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql \watch always ignores \pset null |
Date: | 2014-11-19 05:54:04 |
Message-ID: | 9543.1416376444@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> Hi,
>> /*
>> * Set up rendering options, in particular, disable the pager, because
>> * nobody wants to be prompted while watching the output of 'watch'.
>> */
>> myopt.nullPrint = NULL;
>> myopt.topt.pager = 0;
> I found psql's \watch command always ignores \pset null setting.
> The above source code comment explains why it does,
> but I'd like to see the specified string for null value even in \watch's
> output, in order to distinguish null and an empty value. Thought?
> Is there any reason why \watch must ignore \pset null setting?
Hmmm ... the comment offers a reasonable argument for forcing pager = 0,
but I agree the nullPrint change is not adequately explained.
Will, do you remember why you did that?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2014-11-19 05:55:00 | Re: postgres_fdw behaves oddly |
Previous Message | Michael Paquier | 2014-11-19 05:53:53 | Re: REINDEX CONCURRENTLY 2.0 |