From: | wambacher(at)posteo(dot)de |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: tuple concurrently updated |
Date: | 2018-08-28 14:21:20 |
Message-ID: | 29a5947f-d8b8-377e-d514-62e453646ce8@posteo.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
see postgresql.auto.conf:
# Do not edit this file manually!
# It will be overwritten by ALTER SYSTEM command.
autovacuum = 'true'
shared_buffers = '16GB'
max_stack_depth = '4MB'
autovacuum_max_workers = '4'
work_mem = '1GB'
listen_addresses = '*'
max_connections = '300'
max_worker_processes = '8'
max_parallel_workers_per_gather = '2'
max_wal_size = '4GB'
max_wal_senders = '0'
max_locks_per_transaction = '128'
ssl = 'on'
log_min_messages = 'error'
log_connections = 'off'
log_hostname = 'off'
maintenance_work_mem = '4GB'
log_min_duration_statement = '30000'
checkpoint_completion_target = '0.85'
track_io_timing = 'on'
effective_cache_size = '2GB'
log_checkpoints = 'on'
wal_level = 'minimal'
wal_compression = 'on'
checkpoint_timeout = '5min'
and the storage hardware is on hdd
Am 28.08.2018 um 15:46 schrieb 066ce286(at)free(dot)fr:
> AAMOF, what are your fsync/wal_sync_method parameters, and what is your storage hardware ?
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-08-28 14:33:01 | Re: tuple concurrently updated |
Previous Message | Mario Asboth | 2018-08-28 14:00:42 | Please remove me from the list |