st 22. 5. 2024 v 21:38 odesílatel Ron Johnson
napsal:
> On Wed, May 22, 2024 at 2:02 PM Isaac Morland
> wrote:
>
>> On Wed, 22 May 2024 at 13:48, Ron Johnson
>> wrote:
>>
>> As a superuser administrator, I need to be able to see ALL tables in ALL
>>> schemas when running "\dt", not just the one
On Wed, May 22, 2024 at 2:02 PM Isaac Morland
wrote:
> On Wed, 22 May 2024 at 13:48, Ron Johnson wrote:
>
> As a superuser administrator, I need to be able to see ALL tables in ALL
>> schemas when running "\dt", not just the ones in "$user" and public. And I
>> need it to act consistently acros
On Wed, 22 May 2024 at 13:48, Ron Johnson wrote:
As a superuser administrator, I need to be able to see ALL tables in ALL
> schemas when running "\dt", not just the ones in "$user" and public. And I
> need it to act consistently across all the systems.
>
\dt *.*
But I am skeptical how often yo
On Wed, May 22, 2024 at 1:10 PM Tom Lane wrote:
> Ron Johnson writes:
> > It seems that the search_path of the role that you SET ROLE to does not
> > become the new search_path.
>
> It does for me:
>
> regression=# create role r1;
> CREATE ROLE
> regression=# create schema r1 authorization r1;
>
Ron Johnson writes:
> It seems that the search_path of the role that you SET ROLE to does not
> become the new search_path.
It does for me:
regression=# create role r1;
CREATE ROLE
regression=# create schema r1 authorization r1;
CREATE SCHEMA
regression=# select current_schemas(true), current_us
On 5/22/24 07:27, Ron Johnson wrote:
PG 9.6.24 (Soon, I swear!)
It seems that the search_path of the role that you SET ROLE to does not
become the new search_path.
Am I missing something, or is that PG's behavior?
AS USER postgres
$ psql -h 10.143.170.52 -Xac "CREATE ROLE d
On Wednesday, May 22, 2024, Ron Johnson wrote:
>
>
> It seems that the search_path of the role that you SET ROLE to does not
> become the new search_path.
>
> Am I missing something, or is that PG's behavior?
>
Yes, attaching a setting to a non-login role is basically pointless as
those settings
PG 9.6.24 (Soon, I swear!)
It seems that the search_path of the role that you SET ROLE to does not
become the new search_path.
Am I missing something, or is that PG's behavior?
AS USER postgres
$ psql -h 10.143.170.52 -Xac "CREATE ROLE dbagrp SUPERUSER INHERIT NOLOGIN;"
CREATE
