Re: psql: add \pset true/false
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
From: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
To: michael.paquier@gmail.com
Cc: Jim.Nasby@bluetreble.com, peter_e@gmx.net, tgl@sss.pgh.pa.us,
marko@joh.to,
daniel@manitou-mail.org, pgsql-hackers@postgresql.org
Date: 2015-12-04T08:37:54Z
Lists: pgsql-hackers
Attachments
- psql_column_filter.diff (text/x-patch) patch
- (unnamed) (text/plain)
Hello, I think this is the my last proposal of an idea on psql-side generic solution. Sorry for bothering. > My environment is CentOS7. But completely forgot Windows > environment (or other platforms). I agree with you. It will > indeed too much considering all possible platforms. Ok, DLL is not practical since it would not only be rather complex considering multi platform but used only by this feature and no other user of DLL is not in sight. It's convincing enough for me. Then, how about calling subprocess for purpose? popen() looks to be platform-independent so it is available to call arbitrary external programs or scripts. There are several obvious problems on this. - Tremendously slow since this executes the program for every value. - Dangerous in some aspect. Setting it by environment variable is too dengerous but I'm not confidento whether settig by \pset is safer as acceptable. Is it still too complex? Or too slow? regards, -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
-
Add \pset options for boolean value display
- 645cb44c5490 19 (unreleased) landed