| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:31:17 |
| Message-ID: | 52D7FB45.2060807@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/16/14 4:22 PM, Tom Lane wrote:
> 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.
Completely unscientifically, 50% of the time I've wanted to know the
oprcode has been because I wanted to know its volatility (exactly
because of the stable oprcodes we have). It seemed like a useful
addition, but I don't feel that strongly about it.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Kruse | 2014-01-16 15:32:56 | Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it |
| Previous Message | Tom Lane | 2014-01-16 15:22:46 | Re: Display oprcode and its volatility in \do+ |