fix: do not trigger on views in ContainsPostgresTable

[ggnmstr]

resolves #1000

[Copilot]

Pull request overview

This PR fixes an issue where the ContainsPostgresTable function was incorrectly triggering on database views. The fix adds a check to skip views when determining if a query contains Postgres tables.

Key Changes

• Updated duckdb submodule to a newer commit
• Added filtering logic to exclude views (RELKIND_VIEW) from Postgres table detection

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
third_party/duckdb	Updated submodule commit reference
src/pgduckdb_hooks.cpp	Added view detection to skip views in ContainsPostgresTable function

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The function get_rel_relkind can return 0 if the relation OID is invalid or the relation doesn't exist. This should be checked before comparing against RELKIND_VIEW to avoid silently skipping error cases. Consider adding a check for relkind == 0 and handling it appropriately.

Suggested change

	char relkind = get_rel_relkind(rte->relid);
	char relkind = get_rel_relkind(rte->relid);
	/* get_rel_relkind() returns 0 if the relation does not exist or OID is invalid.
	* Treat such cases as Postgres tables to avoid silently skipping an error. */
	if (relkind == 0) {
	return true;
	}