Postgres Pro
Downloads
Home   >   mailing lists

RE: Protect syscache from bloating with negative cache entries - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject RE: Protect syscache from bloating with negative cache entries
Date
Msg-id 0A3221C70F24FB45833433255569204D1FB6C78A@G01JPEXMBYT05
Whole thread Raw
In response to Re: Protect syscache from bloating with negative cache entries  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Protect syscache from bloating with negative cache entries
List pgsql-hackers
Tree view 
From: Kyotaro HORIGUCHI [mailto:horiguchi.kyotaro@lab.ntt.co.jp]
> 0003: Remote GUC setting
> 
> It is independent from the above two, and heavily arguable.
> 
> pg_set_backend_config(pid, name, value) changes the GUC <name> on the
> backend with <pid> to <value>.
> 

Not having looked at the code yet, why did you think this is necessary?  Can't we always collect the cache stats?  Is
itheavy due to some locking in the shared memory, or sending the stats to the stats collector?
 


Regards
Takayuki Tsunakawa

pgsql-hackers by date:

Previous
From: "Tsunakawa, Takayuki"
Date:
Subject: RE: Libpq support to connect to standby server as priority
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Protect syscache from bloating with negative cache entries