Brian Wipf <brian@xxxxxxxxxxxxxx> writes:
> Nearly 100% of the CPU is going into pmap_remove_range. The stack
> trace for pmap_remove_range, viewable within Shark, is:
> -> pmap_remove_range
> --> pmap_remove
> ---> vm_map_simplify
> ----> vm_map_remove
> -----> task_terminate_internal
> ------> exit1
> -------> exit
> --------> unix_syscall64
> ---------> lo64_unix_scall
In case it's not obvious, this is a kernel performance bug, which
you should report to Apple.
In the meantime you might want to think about backing off your
shared_buffers setting. I would suppose that the performance bug
is being triggered by a very large shared memory segment (you
said 3Gb right?).
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
