Re: CREATE OR REPLACE MATERIALIZED VIEW

From: Aidan Samuel <aidan(dot)samuel(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: CREATE OR REPLACE MATERIALIZED VIEW
Date: 2019-01-10 03:10:46
Message-ID: CAAWhf=N8=G3661QdhLG+L-+TureGrnw_GDD2e4Y3Upm-CHsq9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 10 Jan 2019 at 12:13, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> For indivisible database objects such as functions, IMV the "or replace"
> semantics (COR) is better than the "if not exists" semantics (CINE)...
>
> For tables, though, the tradeoffs seem pretty different...

Thanks Tom, your explanation makes a lot of sense.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Willy-Bas Loos 2019-01-10 11:28:19 log level of "drop cascade" lists
Previous Message Tom Lane 2019-01-10 01:13:47 Re: CREATE OR REPLACE MATERIALIZED VIEW