From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Don't like getObjectDescription results for pg_amop/pg_amproc |
Date: | 2019-08-15 02:20:42 |
Message-ID: | CAPpHfduw54hvxsWmecURGcRf9xysifkyaFh3GCiCMZ1JGkAE9Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 15, 2019 at 2:08 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Or maybe we're just being too ambitious here and we should discard some of
> this information. I'm not really sure that the format_operator result
> can be included without complete loss of intelligibility.
>
> Thoughts? I'm particularly unclear on how any of this might translate
> into other languages, though I doubt that the current text is giving
> good guidance to translators.
Can left and right types of pg_amop mismatch to those of pg_operatror?
It probably could for domains, any* types or something. But for
builtin opclasses they always match.
# select * from pg_amop amop join pg_operator op on op.oid =
amop.amopopr where amop.amoplefttype != op.oprleft or
amop.amoprighttype != op.oprright;
(0 rows)
Could we discard one pair of types from output?
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuro Yamada | 2019-08-15 03:48:21 | Re: [HACKERS] CLUSTER command progress monitor |
Previous Message | Tatsuro Yamada | 2019-08-15 01:45:15 | Re: progress report for ANALYZE |