Re: psql: Add leakproof field to \dAo+ meta-command results
От | Dean Rasheed |
---|---|
Тема | Re: psql: Add leakproof field to \dAo+ meta-command results |
Дата | |
Msg-id | CAEZATCXnnuORE2BoGwHw2zbtVvsPOLhbfVmEk9GxRzK+x3OW-Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: psql: Add leakproof field to \dAo+ meta-command results (Erik Wienhold <ewie@ewie.name>) |
Ответы |
Re: psql: Add leakproof field to \dAo+ meta-command results
|
Список | pgsql-hackers |
> On 2024-07-01 15:08 +0200, Yugo NAGATA wrote: > I would like to propose to add a new field to psql's \dAo+ meta-command > to show whether the underlying function of an operator is leak-proof. > I agree that this is useful information to have, but why add it to \dAo+ instead of \do+? Taking the example from the original thread, when writing a query containing 'tsvector @@ tsquery', it's much more obvious to use "\do+ @@" to check if it's leakproof, rather than "\dAo+ gin". Perhaps it would be useful to have this in \df+ output as well. I notice that this patch spells "leakproof" with a hyphen. IMO leakproof should not have a hyphen -- at least, that's how I naturally spell it, and I think that's more common, and it matches the SQL syntax. We haven't been consistent about that in the docs and code comments so far though, so I think we should make a decision, and then standardise on whatever people decide. Regards, Dean
В списке pgsql-hackers по дате отправления: