Re: Improve LWLock tranche name visibility across backends - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: Improve LWLock tranche name visibility across backends
Date
Msg-id CAA5RZ0txvpg7pZGRt2aUmBck8rVK1nUZkwpu=ehyL6kmHd_apQ@mail.gmail.com
Whole thread Raw
In response to Re: Improve LWLock tranche name visibility across backends  (Sami Imseih <samimseih@gmail.com>)
Responses Re: Improve LWLock tranche name visibility across backends
List pgsql-hackers
> I'll fix this in the next rev.

v5 fixes the above 2 issues found above.

For the issue that was throwing ".... segment that has been freed",
indeed we should be freeing LWLockTrancheNames.shmem->list_ptr,
list_ptr is a dsa_pointer that stores an array of dsa_pointers, which
then made me realize that I was not freeing the actual dsa_pointers
holding the tranche names. I fixed that as well.

I also made some improvements to the code that copies the old
list to the new list and fixed the lookup in
GetLWTrancheName.

--
Sami

Attachment

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Doc: Add note for running ANALYZE after ALTER TABLE ... SET EXPRESSION
Next
From: Chao Li
Date:
Subject: Enhance Makefiles to rebuild objects on map file changes