Re: error_severity of brin work item

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: error_severity of brin work item
Date: 2020-11-13 16:39:31
Message-ID: 20201113163931.GA27443@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2020-Nov-13, Justin Pryzby wrote:

> I saw a bunch of these in my logs:
> log_time | 2020-10-25 22:59:45.619-07
> database |
> left | could not open relation with OID 292103095
> left | processing work entry for relation "ts.child.alarms_202010_alarm_clear_time_idx"
> Those happen following a REINDEX job on that index.
> I think that should be more like an INFO message, since that's what vacuum does
> (vacuum_open_relation), and a queued work item is even more likely to hit a
> dropped relation.

Ah, interesting. Yeah, I agree this is a bug. I think it can be fixed
by using try_relation_open() on the index; if that returns NULL, discard
the work item.

Does this patch solve the problem?

Attachment Content-Type Size
brin-workitems.patch text/x-diff 1.2 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-11-13 16:39:42 Re: [PATCH] Combine same ternary types in GIN and TSearch
Previous Message Tom Lane 2020-11-13 16:26:21 Re: Strange behavior with polygon and NaN