Currently tagbase_schema.sql is executed on every single container startup. This causes issues with all sequences
observation_types_variable_id_seq
submission_submission_id_seq
submission_tag_id_seq
In the instance that the PostGIS container is stopped for any reason, the sequences must be retained. Upon container restart the next sequence value must be incremented otherwise a new submission will attempt to reserve a sequence value which has already been assigned.
I'm discussing this with the container image authors at https://github.com/kartoza/docker-postgis/issues/412
Currently tagbase_schema.sql is executed on every single container startup. This causes issues with all sequences