11 Commits (d1a32a1e7c6520a9bee7c4c1e1cab115807269bf)

Author	SHA1	Message	Date
James Bardin	1338502c7b	Merge pull request #26924 from remilapeyre/concurrent-locks-pg ... Use a global sequence to create the IDs for each workspace	5 years ago
James Bardin	2635b3b023	update remote state to use legacy types	6 years ago
Rémi Lapeyre	d81d521bcd	Use a global sequence to create the IDs for each workspace ... Until now the default workspace for every project would have the ID 1, which would make it impossible to lock them at the same time since we use the ID to identify the lock. With a global sequence to generate the IDs, the default workspace will now have a different ID for each project and it will be possible to lock multiple unrelated projects at the same time. If an old version of Terraform tries to get the lock on a project created with this new version it will work as we continue to use the ID of the workspace, we just change the way we generate them. If this version tries to get a lock on a project created by an old version of Terraform it will work as usual, but we may encounter a conflict with another unrelated project. This is already the current behavior so it's not an issue to persist this behavior. As users migrate to an up-to-date version of Terraform this will stop. Projects already present in the database will keep their conflicting IDs, I did not wanted to change them as users may be reading the states directly in the database for some reason. They can if they want change them manually to remove conflicts, newly created projects will work without manual intervention. Closes https://github.com/hashicorp/terraform/issues/22833	6 years ago
Rémi Lapeyre	12a0a21c0b	Add skip_table_creation and skip_index_creation options to the pg backend ... Closes https://github.com/hashicorp/terraform/issues/25708	6 years ago
Rémi Lapeyre	42be5854a2	Properly quote schema_name in the pg backend configuration	6 years ago
yanndegat	be5280e4e1	remote-state/pg: add option to skip schema creation (#21607) ... * add `skip_schema_creation` option * add sanity check to avoid situations where postgres users hasn't been granted the "CREATE SCHEMA" right closes #21604 Signed-off-by: yann degat <yann@2kmail.net>	7 years ago
Stephen Buergler	fc5b186e8d	Don't leak so many connections in the pg backend ... This change fixes an error I get: Error: pq: too many connections for role "asdf" because I can only have so many connections.	7 years ago
Mars Hall	a075a68c58	Correct name of pg backend‘s default schema	7 years ago
Mars Hall	b9a91b7c1e	Switch pg backend to use native Postgres locks	7 years ago
Mars Hall	d4d798c25e	Fix to use existing pg indexes	7 years ago
Mars Hall	9043005cfb	Postgres database backend	7 years ago