| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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:21:13 |
| Message-ID: | 20190403152113.GA12360@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
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" ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2019-04-03 15:26:20 | Re: Concurrency bug with vacuum full (cluster) and toast |
| Previous Message | Stephen Frost | 2019-04-03 14:43:33 | Re: [PATCH v20] GSSAPI encryption support |