Re: Seems to be impossible to set a NULL search_path

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Seems to be impossible to set a NULL search_path
Дата
Msg-id CAKFQuwYfBP=O9PPjr2aisXDBfy-U5RgDSw+b6YwaTbUquYZiMg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Seems to be impossible to set a NULL search_path  (Bryn Llewellyn <bryn@yugabyte.com>)
Ответы Re: Seems to be impossible to set a NULL search_path  (Bryn Llewellyn <bryn@yugabyte.com>)
Список pgsql-general
On Wed, Jul 13, 2022 at 4:33 PM Bryn Llewellyn <bryn@yugabyte.com> wrote:
  role_name  
-------------
 Bllewell
 Exotic Me
 "Exotic Me"
 "Bllewell"

Of course I understand why I see both Exotic Me with no quotes and "Exotic Me" with double quotes: I asked for it. But why do I see both Bllewell with no quotes and "Bllewell" with double quotes. Are there really two distinct roles with those two names? Or did pg_roles end up with the identifier for the exotic name Bllewell rather than the bare name itself?


You seem perfectly capable of answering those last two questions yourself, better than we who do not have the access to your database; access needed to query pg_roles.

Given that you used UNION ALL I'm not clear why Exotic Me isn't duplicated in the output you profess comes from the test case you wrote.  Is this another one of your mistakes in presenting a self-contained test case?

David J.

В списке pgsql-general по дате отправления:

Предыдущее
От: Bryn Llewellyn
Дата:
Сообщение: Re: Seems to be impossible to set a NULL search_path
Следующее
От: Bryn Llewellyn
Дата:
Сообщение: Re: Seems to be impossible to set a NULL search_path