Re: shared memory size during upgrade pgsql with partitions (max_locks_per_transaction)

>> On Tue, Dec 17, 2019 at 08:03:41PM +, Piotr Włodarczyk wrote: >> Currently we're working on PSQL 11.5 and we're trying upgrade to 12.1. >> >> During that we have a problem: >> >> command: "/usr/pgsql-12/bin/pg_dump" --host /cluster/postgresql --port 50432 >> --username postgres

Re: shared memory size during upgrade pgsql with partitions (max_locks_per_transaction)

On Tue, Dec 17, 2019 at 08:03:41PM +, Piotr Włodarczyk wrote: > Currently we're working on PSQL 11.5 and we're trying upgrade to 12.1. > > During that we have a problem: > > command: "/usr/pgsql-12/bin/pg_dump" --host /cluster/postgresql --port 50432 > --username postgres --schema-only

shared memory size during upgrade pgsql with partitions

Hello, Currently we're working on PSQL 11.5 and we're trying upgrade to 12.1. During that we have a problem: command: "/usr/pgsql-12/bin/pg_dump" --host /cluster/postgresql --port 50432 --username postgres --schema-only --quote-all-identifiers --binary-upgrade --format=custom

Re: Memory size

I was seeing thanks to your recommendations and I found the following, to see what you think cache hit rate 0.99637443599712620769 We have the default values 5 minutes total checkpoint minutes beetween checkpoint 26927 0.358545045634493 temp_files

Re: Memory size

On Sun, Mar 11, 2018 at 10:33 AM, dangal wrote: > jeff thank you very much for your time, I tell you, they are the same > queries > with the same parameters, I take 3 minutes for example, but I execute it > and > it takes me seconds, that's why I suspect it is the

Sv: Memory size

På søndag 11. mars 2018 kl. 13:48:41, skrev dangal >: Dear some consultation, I have a base of about 750 GB in size and we are having problem of slowness in certain views of the application, so I have been seeing it is apparently a