Request a Demo
Home   >   mailing lists

RE: memory leak in logical WAL sender with pgoutput's cachectx - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: memory leak in logical WAL sender with pgoutput's cachectx
Date
Msg-id OSCPR01MB14966752E1D81F2385082EBEBF534A@OSCPR01MB14966.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: memory leak in logical WAL sender with pgoutput's cachectx  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: memory leak in logical WAL sender with pgoutput's cachectx
List pgsql-hackers
Tree view 
Dear Sawada-san,

> Given that cache invalidation is executed upon replaying
> REORDER_BUFFER_CHANGE_INVALIDATION and the end of a transaction
> replay, in which case do we keep the relcache (i.e. just setting
> replicate_valid=false) because of in_use=true?

Per old discussion [1], logicalrep_write_tuple ->SearchSysCache1 can cause the
cache invalidation (I did not verify though).
I felt in this case in_use can be true and validation can be skipped. Thought?

[1]:
https://www.postgresql.org/message-id/OS0PR01MB57168F454E33D53551B8D20294259%40OS0PR01MB5716.jpnprd01.prod.outlook.com

Best regards,
Hayato Kuroda
FUJITSU LIMITED

pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Logical Replication of sequences
Next
From: Antonin Houska
Date:
Subject: Re: Adding REPACK [concurrently]