| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PosTGrESql hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Display oprcode and its volatility in \do+ |
| Date: | 2014-01-16 15:22:46 |
| Message-ID: | 26901.1389885766@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marko Tiikkaja <marko(at)joh(dot)to> writes:
> On 1/16/14 9:53 AM, Rushabh Lathia wrote:
>> Even I personally felt the Function and Volatility is nice to have info
>> into \do+.
FWIW, I'm on board with the idea of printing the oprcode, but adding
volatility here seems like probably a waste of valuable terminal width.
I think that the vast majority of operators have immutable or at worst
stable underlying functions, so this doesn't seem like the first bit
of information I'd need about the underlying function. And why print
this but not, say, security, owner, source code, or other columns
shown in \df? ISTM the value of this addition is to give you what
you need to go look in \df, not to try to substitute for that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2014-01-16 15:31:17 | Re: Display oprcode and its volatility in \do+ |
| Previous Message | Alvaro Herrera | 2014-01-16 15:05:12 | Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ] |