support `\d <table_name>`

[yezizp2012]

BTW, \d <table_name> is not supported.

NTFS, we still need to support OPERATOR like postgreSQL for that. The actual query is as follows:

SELECT c.oid,
  n.nspname,
  c.relname
FROM pg_catalog.pg_class c
     LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
WHERE c.relname OPERATOR(pg_catalog.~) '^(t)$'
  AND pg_catalog.pg_table_is_visible(c.oid)
ORDER BY 2, 3;

Originally posted by @yezizp2012 in #5127 (comment)

[fuyufjh]

WHERE c.relname OPERATOR(pg_catalog.~) '^(t)$'

Oops. This seems a very advanced feature of PG. https://www.postgresql.org/docs/current/xoper.html

I am not sure whether there is a workaround approach for that. Maybe we should remove the "good first issue" tag first.

[xiangjinwu]

In PostgreSQL:

-- `operator` is not reserved as column or table name
test=# create table operator (operator int);
CREATE TABLE
test=# insert into operator values (2);
INSERT 0 1

-- `operator` is not reserved as function name
test=# create function operator (int) returns int return 1;
CREATE FUNCTION

-- This is 2 + (+1)
--             column   syntax      syntax      function           table
test=# select operator operator(+) operator(+) "operator"(9) from operator;
 ?column? 
----------
        3
(1 row)

A little bit challenging for parser / binder.

[github-actions]

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.

[BugenZhao]

BTW, \d+ <table_name> is not supported as well. 😢

[xiangjinwu]

apache/datafusion-sqlparser-rs#548

Noticed upstream support of the PG-specific c.relname OPERATOR(pg_catalog.~) '^(t)$' syntax