From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | yongtaoh2022(at)gmail(dot)com |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18290: \di+ can not show the same name indexes |
Date: | 2024-01-14 15:57:43 |
Message-ID: | 1240720.1705247863@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> gpadmin=# \di+
> List of relations
> Schema | Name | Type | Owner | Table | Persistence | Access method |
> Size | Description
> -----------+------+-------+---------+-------+-------------+---------------+------------+-------------
> pg_temp_3 | idx1 | index | gpadmin | t2 | temporary | btree |
> 8192 bytes |
> (1 row)
> Both table `t1` and temp table `t2` have index idx, but `\di` only shows the
> index of table `t2`.
This is not a bug: \di is operating as documented, namely showing you
the indexes that are visible in your current search_path. The
temp index masks the similarly-named one in public. You could see
both of them with "\di+ *.*", "\di+ *.idx1", or other forms. For
more info see
https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-PATTERNS
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-01-14 17:39:26 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |
Previous Message | Alexander Lakhin | 2024-01-14 12:00:00 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |