Re: Seems to be impossible to set a NULL search_path

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Bryn Llewellyn <bryn(at)yugabyte(dot)com>
Cc: pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Seems to be impossible to set a NULL search_path
Date: 2022-07-14 00:39:03
Message-ID: CAKFQuwYfBP=O9PPjr2aisXDBfy-U5RgDSw+b6YwaTbUquYZiMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 13, 2022 at 4:33 PM Bryn Llewellyn <bryn(at)yugabyte(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bryn Llewellyn 2022-07-14 05:02:44 Re: Seems to be impossible to set a NULL search_path
Previous Message Bryn Llewellyn 2022-07-13 23:33:53 Re: Seems to be impossible to set a NULL search_path