Re: [GENERAL] Difficult while acquiring LWLocks

> AFAIK yes this is the correct way to use multiple lwlocks. > Thanks.! Just curious, Is there any other way to do this.?

[GENERAL] Difficult while acquiring LWLocks

Hi all There is an use case, where i want some 10 LightWeight Locks and after 9.6 LW locks api's (LWLockAssign) are changed a bit and i am confused too. Only reference i cant get was from pg_stat_statement :( Since GetNamedLWLockTranche method will return the base address of the specified

Re: [GENERAL] too may LWLocks

oops its my bad implementation.. I was leaking locks and its fixed now. Thanks for the help! -harry On Thu, Mar 9, 2017 at 1:07 AM, Julien Rouhaud <julien.rouh...@dalibo.com> wrote: > On Wed, Mar 08, 2017 at 03:34:56PM +0530, hariprasath nallasamy wrote: > > Hi all &g

[GENERAL] too may LWLocks

Hi all I am building an extension using shared memory hash table and for locking hash table i am using LWLocks, but the thing was when i try to run some 1k queries one after other, for each query i am getting one LWLock but on executing 200th query i am getting the error *ERROR: too many LWLocks

Re: [GENERAL] Incrementally refreshed materialized view

We also tried to achieve incremental refresh of materialized view and our solution doesn't solve all of the use cases. Players: 1) WAL 2) Logical decoding 3) replication slots 4) custom background worker Two kinds of approaches : 1. Deferred refresh (oracle type of creating log table for each

[GENERAL] Replication slot on master failure

Hi all We are using replication slot for capturing some change sets to update dependent tables. Will there be inconsistency if the master fails and the standby takes the role of master.? cheers -harry