Hi moran and others; yesterday i get the pg problem again, and i use perf top Observation follows:PerfTop: 11574 irqs/sec kernel: 2.2% exact: 0.0% [4000Hz cycles], (all, 32 CPUs) 81.39% postgres [.] s_lock 5.42% postgres [.] LWLockAcquire 4.59% postgres [.] LWLockRelease 3.06% postgres [.] TransactionIdIsInProgress 0.38% postgres [.] PinBuffer 0.31% postgres [.] TransactionIdPrecedes 0.27% postgres [.] UnpinBuffer 0.19% postgres [.] TransactionIdIsCurrentTransactionId 0.16% postgres [.] heap_hot_search_buffer 0.15% [kernel] [k] number.isra.1 0.14% [kernel] [k] kallsyms_expand_symbol.constprop.1 0.10% [kernel] [k] module_get_kallsym 0.10% libc-2.17.so [.] __strcmp_sse42 0.09% [kernel] [k] _raw_spin_lock 0.09% postgres [.] hash_search_with_hash_valueis spin lock problem ? I need everyone's help to solve the problem.thsnks!
pgsql-general by date:
Соглашаюсь с условиями обработки персональных данных