Re: autovacuum big table taking hours and sometimes seconds

On Thu, Feb 7, 2019 at 6:55 AM Mariel Cherkassky < mariel.cherkas...@gmail.com> wrote: I have 3 questions : > 1)To what value do you recommend to increase the vacuum cost_limit ? 2000 > seems reasonable ? Or maybe its better to leave it as default and assign a > specific value for big tables ? >

Managing High Availability in PostgreSQL – Part I

Managing high availability in your PostgreSQL hosting is very important to ensuring your clusters maintain exceptional uptime and strong operational performance so your data is always available to your application. In an earlier blog post, we introduced you

Re: autovacuum big table taking hours and sometimes seconds

Just to make sure that I understood : -By increasing the cost_limit or decreasing the cost of the page_cost we can decrease the time it takes the autovacuum process to vacuum a specific table. -The vacuum threshold/scale are used to decide how often the table will be vacuum and not how long it shou

Re: Transaction size and Wal2Json

On 07/02/2019 11:38, Mai Peng wrote: > We use the plugin Wal2Json in order to catch every modification on database. > We’ve got an issue : WAL were growing very fast, the state of > pg_stat_replication still on ‘catchup’ , an error:pg_recvlogical: unexpected > termination of replication stream:

Transaction size and Wal2Json

Hello, We use the plugin Wal2Json in order to catch every modification on database. We’ve got an issue : WAL were growing very fast, the state of pg_stat_replication still on ‘catchup’ , an error:pg_recvlogical: unexpected termination of replication stream: ERROR: out of memory DETAIL: Cannot e