fix: Add postgres compatibility in HiveTableLastUpdatedExtractor

[chonyy]

Summary of Changes

• Related issue: Hive Metastore PostgreSQL compatibility issue on extractors #1608
• Similar PR: fix: Add postgres compatibility in PrestoViewMetadataExtractor #1878
• Currently, HiveTableLastUpdatedExtractor is only workable with MySQL connection string. The syntax of the SQL statement is not compatible with Postgres
• Followed the method in HiveTableMetadataExtractor
  • Added SQL statement for Postgres
  • Added a helper function to choose the SQL statement based on the connection string

Tests

This change has been running in our production environment for a couple of months. I believe no additional unit test is needed since it's simply fixing an unexpected behavior.

CheckList

Make sure you have checked all steps below to ensure a timely review.

• PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.
• PR includes a summary of changes.
• PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain docstrings that explain what it does

[chonyy]

Same unit test import problem as mentioned here: #1878 (comment)

[feng-tao]

@chonyy could you rebase and fix the CI? will take a look once it is updated. sorry for the late

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[chonyy]

Hi @feng-tao , all ci unit tests are passed. Pls help me take a look at it when you have time, thanks 🙏

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.