You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Primary keys are automatically indexes in Postgres, specially tagged via the indisprimary column in pg_index;
In RisingWave, our pg_index only shows indexes created via CREATE INDEX.
Since we do not have other ways around to show all indexes and PKs within a database schema in a single query, we have to iterate over all tables and query through show columns from <rel>. This is very inconvenient and error-prone.
Describe the solution you'd like
We should at least include primary keys in pg_index and consider adding them to rw_indexes;
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
For PKs, what content should we fill in column indexdef? Should we leave it empty or construct a fake one like CREATE UNIQUE INDEX XXXX_index ON public.XXXX USING btree (col1, col2)?
Is your feature request related to a problem? Please describe.
Primary keys are automatically indexes in Postgres, specially tagged via the indisprimary column in pg_index;
In RisingWave, our pg_index only shows indexes created via
CREATE INDEX
.Since we do not have other ways around to show all indexes and PKs within a database schema in a single query, we have to iterate over all tables and query through
show columns from <rel>
. This is very inconvenient and error-prone.Describe the solution you'd like
We should at least include primary keys in pg_index and consider adding them to rw_indexes;
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: