Re: Display oprcode and its volatility in \do+ - Mailing list pgsql-hackers

From Marti Raudsepp
Subject Re: Display oprcode and its volatility in \do+
Date
Msg-id CABRT9RAwHNSKMJBaBi4PaH+O-X2T1Ac6ZEQsLriRTxSvEBry3A@mail.gmail.com
Whole thread Raw
In response to Re: Display oprcode and its volatility in \do+  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Jan 16, 2014 at 5:22 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

For a data point, just today I wanted to look up the volatility of
pg_trgm operators, which made me remember this patch. The \do+ output
is narrow enough, I think an extra volatility column wouldn't be too
bad.

But even just having the function name is a huge improvement, at least
that allows looking up volatility using \commands without accessing
pg_operator directly.

Regards,
Marti



pgsql-hackers by date:

Previous
From: Ronan Dunklau
Date:
Subject: Proposal: IMPORT FOREIGN SCHEMA statement.
Next
From: Atri Sharma
Date:
Subject: Re: Proposal: IMPORT FOREIGN SCHEMA statement.