Re: Implementing Incremental View Maintenance

From: Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>
To: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Takuma Hoshiai <hoshiai(at)sraoss(dot)co(dot)jp>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, Michael Paquier <michael(at)paquier(dot)xyz>, Amit Langote <amitlangote09(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, kgrittn(at)gmail(dot)com
Subject: Re: Implementing Incremental View Maintenance
Date: 2020-07-07 03:11:08
Message-ID: CAKU4AWoSv-ok0kncP9vmL2V-hbcrQ3hgXCFipXiFkWVuQh-Qrg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks for the patch!

> Query checks for following restrictions are added:

Are all known supported cases listed below?

> - inheritance parent table
> ...
> - targetlist containing IVM column
> - simple subquery is only supported
>

How to understand 3 items above?

-
Best Regards
Andy Fan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message movead.li@highgo.ca 2020-07-07 03:22:46 Re: pg_resetwal --next-transaction-id may cause database failed to restart.
Previous Message Amit Kapila 2020-07-07 03:10:13 Re: Resetting spilled txn statistics in pg_stat_replication