Re: tuple concurrently updated
От | wambacher@posteo.de |
---|---|
Тема | Re: tuple concurrently updated |
Дата | |
Msg-id | 29a5947f-d8b8-377e-d514-62e453646ce8@posteo.de обсуждение исходный текст |
Ответ на | Re: tuple concurrently updated (066ce286@free.fr) |
Список | 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@free.fr: > AAMOF, what are your fsync/wal_sync_method parameters, and what is your storage hardware ? >
В списке pgsql-admin по дате отправления: