Add a check for identifiers with maximum length

[mfvanek]

By default identifier length is bounded with 63 bytes.
When any identifier (table/index/sequence name) is out of this range PostgreSQL will silently truncate the identifier name. No errors are raised.
It might be confusing for developers in case of two identifiers with long names that differ a bit at the ending:

create index concurrently if not exists my_custom_index_on_my_custom_table_with_very_loooooooooooooooooooong_name_on_field1
    on my_custom_table (field1);
create index concurrently if not exists my_custom_index_on_my_custom_table_with_very_loooooooooooooooooooong_name_on_field2
    on my_custom_table (field2);

For first index you will get a warning with sql state 42622 like:
identifier "my_custom_index_on_my_custom_table_with_very_loooooooooooooooooooong_name_on_field1" will be truncated to "my_custom_index_on_my_custom_table_with_very_looooooooooooooooo"
and index will be created with truncated name.

For second index you'll get a warning:
relation "my_custom_index_on_my_custom_table_with_very_looooooooooooooooo" already exists, skipping and no index

[mfvanek]

Flyway with Teams subscription probably can help. See Error Overrides option:
.errorOverrides("42622:0:E")

[mfvanek]

We can find all identifiers with maximum length and report them.
It will not be a very accurate check but sometimes it can be useful.