| From: | Wolfgang Walther <walther(at)technowledgy(dot)de> |
|---|---|
| To: | Abdul Qoyyuum <aqoyyuum(at)cardaccess(dot)com(dot)au> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ALTER ROLE ... SET in current database only |
| Date: | 2021-02-16 08:41:07 |
| Message-ID: | 260e6e0d-acf7-40be-601e-9dd2c7ce2add@technowledgy.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | João Gaspar | 2021-02-16 09:50:49 | Re: [LDAPS] Test connection user with ldaps server |
| Previous Message | Thomas Kellerer | 2021-02-16 06:52:09 | Re: Turn jit off for slow subquery in Postgres 12 |