Re: [GENERAL] Out of shared memory (locks per process) using table-inheritance style partitioning

So what's the problem? Increase max_locks_per_transaction. The reason we have that as a tunable is mainly to support systems with very large numbers of tables. So increasing this value into the thousands is a reasonable approach? If it is reasonable, that's fine. I'll certainly be

Re: [GENERAL] Out of shared memory (locks per process) using table-inheritance style partitioning

John Prevost [EMAIL PROTECTED] writes: So what's the problem? Increase max_locks_per_transaction. The reason we have that as a tunable is mainly to support systems with very large numbers of tables. So increasing this value into the thousands is a reasonable approach? If it is reasonable,

[GENERAL] Out of shared memory (locks per process) using table-inheritance style partitioning

I've recently been developing for work a website backed by PostgreSQL, showing information about network flows. This data is extremely high volume in places, and I was hard pressed to come up with a good way to speed up data loading times until I came across the recommendation to use table

Re: [GENERAL] Out of shared memory (locks per process) using table-inheritance style partitioning

John Prevost [EMAIL PROTECTED] writes: So, what's the problem? Well=97I have twelve tables that are partitioned by hour. There are 24 hours in a day, there are seven days in a week, and... you may see where I'm going here. PostgreSQL gets a lock on each individual table queried (in this