Re: Refresh Materialized View Issue - Mailing list pgsql-general

From Jeremiah Bauer
Subject Re: Refresh Materialized View Issue
Date
Msg-id CH2PR19MB3576ED0CE09DF08D35E3BBFAC2682@CH2PR19MB3576.namprd19.prod.outlook.com
Whole thread Raw
In response to Re: Refresh Materialized View Issue  (Ron Johnson <ronljohnsonjr@gmail.com>)
Responses Re: Refresh Materialized View Issue  (Ron Johnson <ronljohnsonjr@gmail.com>)
List 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


CONFIDENTIALITY NOTICE: The information contained in this email (and any attachments) is privileged and confidential and protected from disclosure. If you are not the intended recipient of this email or the attachments, be aware that any disclosure, copying, distribution or use of this email or any attachment is strictly prohibited and you should not read the message or read or open any attachment. If you have received this email by mistake, please immediately notify the sender and delete it permanently from your system. Agri Stats, Inc. and its subsidiaries will not be held liable to any person or entity resulting from the unintended or unauthorized use of any information contained in this email.

pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Refresh Materialized View Issue
Next
From: Adrian Klaver
Date:
Subject: Re: Time zone offset in to_char()