Re: Understanding max_locks_per_transaction

2023-10-16 Thread Ron
On 10/16/23 14:31, Craig McIlwee wrote: That's what we've already done for the short term solution.  It is somewhat in conflict with your statement regarding the number of lockable objects not holding still for long, though.  As time goes on and our scheduled jobs automatically create new

Re: Understanding max_locks_per_transaction

2023-10-16 Thread Craig McIlwee
On Mon, Oct 16, 2023 at 2:32 PM Tom Lane wrote: > Craig McIlwee writes: > > Most discussions regarding the lock table say that the size of the lock > > table determines how many locks can be held. The documentation for > > max_locks_per_transaction [3] reads slightly different though, and in >

Re: Understanding max_locks_per_transaction

2023-10-16 Thread Tom Lane
Craig McIlwee writes: > Most discussions regarding the lock table say that the size of the lock > table determines how many locks can be held. The documentation for > max_locks_per_transaction [3] reads slightly different though, and in > particular this phrases stands out to me: >> no more

Understanding max_locks_per_transaction

2023-10-16 Thread Craig McIlwee
We're using PostgreSQL 13.10, installed on CentOS 7 from PGDG RPMs. Recently we've run into "out of shared memory" issues with a hint at increasing max_locks_per_transaction. The problem is well described in the PostgreSQL documentation and various blog posts found around the internet, and the

Re: Question About PostgreSQL Extensibility

2023-10-16 Thread Laurenz Albe
On Fri, 2023-10-13 at 13:55 +, felix.quin...@yahoo.com wrote: > For the same reason that you can use python or perl in postgresql. It's just > another language. > I have .net code running on several sql servers and to change the database to > postgresql I have to reprogram them. Yes, you'll

Re: Purely declarative FKs

2023-10-16 Thread Ron
On 10/16/23 09:06, Tom Lane wrote: Christophe Pettus writes: On Oct 16, 2023, at 00:51, Thiemo Kellner wrote: Question: Are there plans to provide a feature in PostgreSQL that one can have foreign keys for purely documentation purpose - I know, one could use a modelling tool and just not

Re: Purely declarative FKs

2023-10-16 Thread Tom Lane
Christophe Pettus writes: > On Oct 16, 2023, at 00:51, Thiemo Kellner wrote: >> Question: Are there plans to provide a feature in PostgreSQL that one >> can have foreign keys for purely documentation purpose - I know, one >> could use a modelling tool and just not implement the FKs, but my >>

Re: Postgresql HA cluster

2023-10-16 Thread Jehan-Guillaume de Rorthais
On Fri, 13 Oct 2023 19:21:46 + Laura Smith wrote: > --- Original Message --- > On Friday, October 13th, 2023 at 14:10, Jehan-Guillaume de Rorthais > wrote: > > > But really, double check first why a simple primary-standby architecture > > doesn't meet your needs. The simpler the

Re: Purely declarative FKs

2023-10-16 Thread Christophe Pettus
> On Oct 16, 2023, at 00:51, Thiemo Kellner wrote: > Question: Are there plans to provide a feature in PostgreSQL that one can > have foreign keys for purely documentation purpose - I know, one could use a > modelling tool and just not implement the FKs, but my reality is, there is > hardly

Purely declarative FKs

2023-10-16 Thread Thiemo Kellner
Hi Please bear with me, if this is the wrong place or this is an old question answered over and over again. Context: In my professional life I rarely come across projects/applications where there are foreign keys on the database. This is due to loading freedom not due to that there actually