Re: Performance degradation of REFRESH MATERIALIZED VIEW - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Performance degradation of REFRESH MATERIALIZED VIEW
Date
Msg-id CAH2-Wzm0b6a6a4x1ObE2SH_S-UEdmd32_sfBmxcjoJ4QHjEcUQ@mail.gmail.com
Whole thread Raw
In response to Re: Performance degradation of REFRESH MATERIALIZED VIEW  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Tue, May 11, 2021 at 11:46 AM Andrew Dunstan <andrew@dunslane.net> wrote:
> > Yes, reverting has its place.  Moreover, threats of reversion have their
> > place.  People should definitely be working towards finding solutions to
> > the problems in their commits lest they be reverted.  However, freezing
> > *people* by saying that no fixes are acceptable other than reverts ...
> > is not good.
> >
> > So I agree with what Andres is saying downthread: let's apply the fix he
> > proposed (it's not even that invasive anyway), and investigate the
> > remaining 5% and see if we can find a solution.  If by the end of the
> > beta process we can definitely find no solution to the problem, we can
> > revert the whole lot then.
> >
>
>
> I agree with all of this. Right now I'm only concerned if there isn't
> work apparently being done on some issue.

+1. While reverting a patch is always on the table, it must be the
option of last resort. I don't have any specific reason to believe
that that's the point we're at just yet.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: compute_query_id and pg_stat_statements
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: compute_query_id and pg_stat_statements