From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | yuzuko <yuzukohosoya(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, David Steele <david(at)pgmasters(dot)net>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Amit Langote <amitlangote09(at)gmail(dot)com>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Greg Stark <stark(at)mit(dot)edu> |
Subject: | Re: Autovacuum on partitioned table (autoanalyze) |
Date: | 2021-04-07 03:33:46 |
Message-ID: | 20210407033346.GA3434@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021-Apr-07, yuzuko wrote:
> I'm working on fixing the patch according to the comments.
> I'll send it as soon as I can.
Thanks, I've been giving it a look too.
> I've been thinking about traditional inheritance, I realized that we
> need additional
> handling to support them because unlike declarative partitioning,
> parents may have
> some rows in the case of traditional inheritance as Alvaro mentioned.
> So I think we should support only declarative partitioning in this
> patch for now,
> but what do you think?
Yeah, not fixable at present I think.
> I'm not sure but if we can solve this matter at low cost by using the
> shared memory stats patch, should we wait for the patch?
Let's do that for 15.
--
Álvaro Herrera 39°49'30"S 73°17'W
"The problem with the future is that it keeps turning into the present"
(Hobbes)
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Dilger | 2021-04-07 05:03:50 | Re: multi-install PostgresNode fails with older postgres versions |
Previous Message | Kazutaka Onishi | 2021-04-07 03:30:00 | Re: TRUNCATE on foreign table |