postgresql_database search_path

[OJFord]

[Removed the template because not a bug]

Currently it doesn't seem to be possible to set the database-level search_path on the postgresql_database resource; it's necessary to create the resource and then connect and ALTER DATABASE dbname SET search_path TO schema1,schema2,schema3; some other way afterwards.

It would be good to have a list(string) argument on postgresql_database to set this instead:

resource "postgresql_database" "db" {
  name = "dbname"
  owner = "me"
  search_path = [
    "\"$user\"",
    "public",
    "myadditionalschema",
  ]
}

Hope to have a PR shortly.

[OJFord]

Hope to have a PR shortly.

Actually, sorry, but since I just found it is supported on the role I can do it like that for now. I might still get around to it though 🙂

[joaocc]

Hi
Is there any update on this?
We are looking into specifying search_path per DB for a specific user

ALTER ROLE xxx IN DATABASE db1 SET search_path TO schema_1

The current provider only supports, which is not enough for the current application we are managing here

ALTER ROLE xxx db1 SET search_path TO schema_1

In our case, we are using search_path in a connection string, which is not supported by pgbounce, thus, requiring setting it on the user.

[OJFord]

Not from me, we're still working around the original desire with it on the role.

Note this issue is about:

ALTER DATABASE db1 SET search_path TO schema_1

(not alter role in any variation)

[joaocc]

Thx for the clarification. Will just created a new ticket to for our request (#526).