Request a Demo
Home   >   mailing lists

Unexpected changes of CurrentResourceOwner and CurrentMemoryContext - Mailing list pgsql-hackers

From Antonin Houska
Subject Unexpected changes of CurrentResourceOwner and CurrentMemoryContext
Date
Msg-id 119497.1756892972@localhost
Whole thread Raw
Responses Re: Unexpected changes of CurrentResourceOwner and CurrentMemoryContext
List pgsql-hackers
Tree view 
When working on the REPACK command, we see an ERROR caused by unexpected
change of CurrentResourceOwner [1]. I think the problem is that
reorderbuffer.c does not restore the original value after calling
RollbackAndReleaseCurrentSubTransaction(). The attached patch tries to handle
the call like other callers throughout the tree do.

[1]
https://www.postgresql.org/message-id/CADzfLwUgPMLiFkXRnk97ugPqkDfsNJ3TRdw9gjJM%3D8WB4_nXwQ%40mail.gmail.com

-- 
Antonin Houska
Web: https://www.cybertec-postgresql.com
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: 回复: Fix segfault while accessing half-initialized hash table in pgstat_shmem.c
Next
From: Ajin Cherian
Date:
Subject: Re: Improve pg_sync_replication_slots() to wait for primary to advance