Fixes incorrect behaviour of the option deduplicate items after creating the index #8969

[mzabuawala]

This PR modifies the SQL query used to retrieve the index metadata to accurately process reloptions for defaults of PostgreSQL index types. Some options, such as fillfactor, deduplicate_items and others, would return NULL when not set, irrespective of internal defaults within PostgreSQL. This would cause misleading or incomplete information regarding the index.

Applied index-type specific defaults when reloptions are not explicitly set:

• B-tree: fillfactor = 100, deduplicate_items = true
• GiST: fillfactor = 90, buffering = 'auto'
• GIN: fastupdate = true, gin_pending_list_limit = 4MB
• BRIN: pages_per_range = 128, autosummarize = false

[akshay-joshi]

Hi Murtuza,

I did a quick review, and according to the PostgreSQL documentation, deduplicate_items was introduced in version 13 and above. Therefore, any changes involving this feature in the default folder or "properties.sql" for versions below 13 will result in an error.

Since pgAdmin's default folder maps to PostgreSQL version 10, please address this issue accordingly.

Once you've made the necessary fixes, I'll proceed with testing your PR.

[akshay-joshi]

Hi Murtuza,

I did a quick review, and according to the PostgreSQL documentation, deduplicate_items was introduced in version 13 and above. Therefore, any changes involving this feature in the default folder or Properties.sql for versions below 13 will result in an error.

Since pgAdmin's default folder maps to PostgreSQL version 10, please address this issue accordingly.

Once you've made the necessary fixes, I'll proceed with testing your PR.

Review need to block merge