Re: CREATE/REFRESH MATERIALIZED VIEW planner difference?

From: Philip Semanchuk <philip(at)americanefficient(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: CREATE/REFRESH MATERIALIZED VIEW planner difference?
Date: 2021-06-02 12:39:33
Message-ID: 083DF3BE-BD4D-411B-956A-3BBF7448D688@americanefficient.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Jun 1, 2021, at 3:23 PM, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>
> On Wed, Jun 2, 2021 at 7:15 AM Vijaykumar Jain
> <vijaykumarjain(dot)github(at)gmail(dot)com> wrote:
>> i only get workers to create mv, but refresh mv plan does not use workers for the same conf params.
>
> Yeah, this changed in v14:
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=9e7ccd9ef64d05e87ceb1985d459bef9031205c0

Thanks, all! It’s great to have a clear explanation. I looked at the change notes for 12 & 13 before I posted. I didn’t occur to me to look at 14. :-)

Cheers
Philip

In response to

Browse pgsql-general by date

  From Date Subject
Next Message gerry gan 2021-06-03 01:34:46 Re: Is consistent (deterministic) ordering possible in our case?
Previous Message Laurenz Albe 2021-06-02 08:43:42 Re: Internationalisation (i18n) with Postgres as backend