From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Concurrency bug with vacuum full (cluster) and toast |
Date: | 2019-04-03 15:26:20 |
Message-ID: | 20190403152620.GF6197@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Justin Pryzby (pryzby(at)telsasoft(dot)com) wrote:
> On Fri, Mar 22, 2019 at 02:27:07PM -0400, Robert Haas wrote:
> > On Tue, Mar 19, 2019 at 1:37 PM Alexander Korotkov
> > <a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> > > Thank you for pointing, but none of the threads you pointed describe
> > > this exact problem. Now I see this bug have a set of cute siblings :)
> >
> > Yeah. I really thought this precise issue -- the interlocking between
> > the VACUUM of the main table and the VACUUM of the TOAST table -- had
> > been discussed somewhere before. But I couldn't find that discussion.
>
> That also describes the longstanding issue with pg_statistic / pg_toast_2619,
> no ?
>
> I think that's maybe what Robert is remembering, and searching for
> pg_toast_2619 gives a good number of results (including my own problem report).
>
> Is this an "Opened Item" ?
If you're referring to the v12 open items list, then, no, I wouldn't
think it would be as it's not a new issue (unless I've misunderstood).
Only regressions from prior versions are appropriate for the v12 open
items list, long-standing bugs/issues should be addressed and fixed, of
course, but those would be fixed and then back-patched.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2019-04-03 15:55:00 | Re: New vacuum option to do only freezing |
Previous Message | Justin Pryzby | 2019-04-03 15:21:13 | Re: Concurrency bug with vacuum full (cluster) and toast |