Re: Refresh Materialized View Issue
От | Jeremiah Bauer |
---|---|
Тема | Re: Refresh Materialized View Issue |
Дата | |
Msg-id | CH2PR19MB3576ED0CE09DF08D35E3BBFAC2682@CH2PR19MB3576.namprd19.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: Refresh Materialized View Issue (Ron Johnson <ronljohnsonjr@gmail.com>) |
Ответы |
Re: Refresh Materialized View Issue
|
Список | pgsql-general |
My question is: what indexes are on public.large_table? Hopefully there's a compound b-tree index on id1, id2, id3.
There is not, after further investigation. There are these 4 indexes that involve id1, id2, and id3. Should I try creating an index on all three of the columns?
CREATE INDEX IF NOT EXISTS idx_large_table_id1
ON public.large_table USING btree
(id1 ASC NULLS LAST)
TABLESPACE pg_default;
CREATE INDEX IF NOT EXISTS idx_large_table_id2
ON public.large_table USING btree
(id2 ASC NULLS LAST)
TABLESPACE pg_default;
CREATE INDEX IF NOT EXISTS idx_large_table_id3
ON public.large_table USING btree
(id3 ASC NULLS LAST)
TABLESPACE pg_default;
CREATE INDEX IF NOT EXISTS idx_large_table_id2_id3
ON public.large_table USING btree
(id2 ASC NULLS LAST, id3 ASC NULLS LAST)
TABLESPACE pg_default;
A materialized view isn't too different from an unlogged table.
So an unlogged table would also be an appropriate solution?
--
Jeremiah
В списке pgsql-general по дате отправления: