Contention on LWLock buffer_content, due to SHARED lock(?)

2019-12-09 Thread Jens-Wolfhard Schicke-Uffmann
Hi, today I observed (on a r5.24xlarge AWS RDS instance, i.e. 96 logical cores) lock contention on a buffer content lock due to taking of a SHARED lock (I think): Three tables were involved, simplified case: CREATE TABLE global_config (id BIGINT PRIMARY KEY); CREATE TABLE b ( id BIGINT PRIMAR

Re: Contention on LWLock buffer_content, due to SHARED lock(?)

2019-12-10 Thread Jens-Wolfhard Schicke-Uffmann
Hi, On Tue, Dec 10, 2019 at 08:44:17AM -0800, Andres Freund wrote: > > today I observed (on a r5.24xlarge AWS RDS instance, i.e. 96 logical > > cores) lock contention on a buffer content lock due to taking of a > > SHARED lock (I think): > When you say "7000 active transactions" - do you mean to s

Re: Contention on LWLock buffer_content, due to SHARED lock(?)

2019-12-10 Thread Jens-Wolfhard Schicke-Uffmann
Hi, On Tue, Dec 10, 2019 at 03:07:05PM -0300, Alvaro Herrera wrote: > I'd rather have the ability to mark a table READ ONLY (or similar). > Then any FK references can skip the row locks altogether. For the rare > cases where you need to modify the referenced table, have it marked READ > WRITE, an

Parameter binding for COPY TO queries

2025-02-14 Thread Jens-Wolfhard Schicke-Uffmann
Hi, I'd like some input on the idea of adding parameter binding support to queries executed as part of a COPY TO command. Is there a technical or philosophical reason why these queries should not contain bindable parameters? As far as I could ascertain, the feature has been desired for a long tim