Schema validation fails with same name sequences in different schemas

Description

Using multiple schemas with same name sequences but different parameters.
I use a default schema name, but the sequence information extractor retrieves all sequences and database information is initialized with sequences devoid of schema name in the order received from the extractor.
So if the result is a sequence from default schema followed by the same sequence from another schema, it will be overwritten with invalid information from another schema.

Extractor uses select * from information_schema.sequences to get all sequences disregarding any default schema configuration.

Then, DatabaseInformationImpl.java populates sequenceInformationMap in order received from executing the above sql, removing schema qualifier and overwriting without any check. source

Environment

Postgres 11

Assignee

Unassigned

Reporter

Alex CD

Fix versions

None

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Affects versions

Priority

Critical
Configure