lean parameter named log_copy?
Corresponding patch is attached.
This is a useful feature I was waiting for some time.
If some application which workload you want to collect is using COPY
statement, then recording network traffic was your only option.
--
Grigory Smolkin
Postgre
On 09/05/2016 04:34 PM, Alvaro Herrera wrote:
Grigory Smolkin wrote:
Funny part is that it never drops them. So when backend is finally
terminated, it tries to drop them and fails with error:
FATAL: out of shared memory
HINT: You might need to increase max_locks_per_transaction
If I
pages: 0 removed, 68225 remain, 0 skipped due to pins
tuples: 0 removed, 2458382 remain, 2408081 are dead but not yet
removable
buffer usage: 146450 hits, 31 misses, 0 dirtied
avg read rate: 0.010 MB/s, avg write rate: 0.000 MB/s
system usage: CPU 3.27s/6.92u sec elapsed 2
