| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Poll: are people okay with function/operator table redesign? |
| Date: | 2020-04-20 14:21:14 |
| Message-ID: | 11667.1587392474@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Victor Yegorov <vyegorov(at)gmail(dot)com> writes:
> While table 9.5 with functions looks quite nice, I quite dislike 9.4 with
> operators.
> Previously, I could lookup operator in the leftmost column and read on.
> Right now I have to look through the whole table (well, not really, but
> still) to find the operator.
Aside from the alternatives already discussed, the only other idea
that's come to my mind is to write operator entries in a style like
|| as in: text || text → text
Concatenates the two strings.
'Post' || 'greSQL' → PostgreSQL
Not sure that that's any better, but it is another alternative.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonin Houska | 2020-04-20 14:31:13 | Re: More efficient RI checks - take 2 |
| Previous Message | Magnus Hagander | 2020-04-20 14:15:10 | Re: Allow pg_read_all_stats to read pg_stat_progress_* |