Re: WARNING: missing lock on database "postgres" (OID 5) @ TID (0,4)

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, noah(at)leadboat(dot)com
Subject: Re: WARNING: missing lock on database "postgres" (OID 5) @ TID (0,4)
Date: 2024-12-09 11:50:16
Message-ID: CALdSSPhL6=42GKC75fzf-yoSR-YRczUy03zWrKvZbKcoS1Mb2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 9 Dec 2024 at 15:27, Alexander Kukushkin <cyberdemn(at)gmail(dot)com> wrote:

> postgres=# reassign owned by test to postgres;
> WARNING: missing lock on database "postgres" (OID 5) @ TID (0,4)
> REASSIGN OWNED

Hi!
Looks like PFA should fix that.

--
Best regards,
Kirill Reshke

Attachment Content-Type Size
v1-0001-Lock-tuple-for-inplace-update-when-moidfying.patch application/octet-stream 1.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2024-12-09 12:17:03 Re: Wrong results with right-semi-joins
Previous Message Dilip Kumar 2024-12-09 11:48:30 Re: Track the amount of time waiting due to cost_delay