Re: ALTER ROLE ... SET in current database only - Mailing list pgsql-general

From Wolfgang Walther
Subject Re: ALTER ROLE ... SET in current database only
Date
Msg-id 260e6e0d-acf7-40be-601e-9dd2c7ce2add@technowledgy.de
Whole thread Raw
In response to Re: ALTER ROLE ... SET in current database only  (Abdul Qoyyuum <aqoyyuum@cardaccess.com.au>)
List pgsql-general
Abdul Qoyyuum:
> Wouldnt you need to connect to the database first before you can ALTER 
> ROLE anything?

Of course, otherwise the notion of "current database" wouldn't make 
sense at all. But that's only before executing the code. I am not 
writing and executing this code at the same time.

In my case I'm seeding a postgres docker container with settings and 
data on first launch. The database name is passed to the container via 
environment variable. But, I'm sure there are other use-cases where code 
should be written once, but be executed in different databases.

Best,

Wolfgang



pgsql-general by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: Turn jit off for slow subquery in Postgres 12
Next
From: João Gaspar
Date:
Subject: Re: [LDAPS] Test connection user with ldaps server