Re: Is it worth to optimize VACUUM/ANALYZE by combining duplicate rel instances into single rel instance?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: bharath(dot)rupireddyforpostgres(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Is it worth to optimize VACUUM/ANALYZE by combining duplicate rel instances into single rel instance?
Date: 2021-04-21 02:50:35
Message-ID: YH+S+96YAjHscyxA@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 21, 2021 at 11:32:49AM +0900, Kyotaro Horiguchi wrote:
> On the other hand the patch creates a relation list just for this
> purpose, which is not needed to run VACUUM/ANALYZE, and VACUUM/ANALYE
> works well with duplicates in target relations.

Yeah, I don't think either that this is worth spending cycles on, not
to mention that the current behavior could be handy as VACUUM uses
separate transactions for each relation vacuumed if more than one
relation is listed in the set.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Fan 2021-04-21 02:55:29 prerequisites of pull_up_sublinks
Previous Message tsunakawa.takay@fujitsu.com 2021-04-21 02:41:58 RE: [bug?] Missed parallel safety checks, and wrong parallel safety