Re: [GENERAL] time series data

On Mon, Oct 2, 2017 at 10:27 AM, Khalil Khamlichi wrote: > we have records like this > > ccdb1=# select user_name, agent_status, event_time from cc_events ; > > user_name | agent_status | event_time > ---+--+- > user1 |

Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common

Hi Craig, Anyway, this OS is guess OS in vmware (vsphere). Thank for your response and help. On Tue, Oct 3, 2017 at 8:49 PM, Craig Ringer wrote: > > > Can you get stacks please? > > Use -g > # Events: 2K cpu-clock # # Overhead Command Shared Object

Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common

On 3 October 2017 at 19:45, milist ujang wrote: > Hi all, > > I've an environment 9.4 + bdr: > PostgreSQL 9.4.4 > You're on a pretty old postgres-bdr. Update. You're missing a lot of fixes from mainline. > This is consolidation databases, in this machine there are

[GENERAL] BDR, wal sender, high system cpu, mutex_lock_common

Hi all, I've an environment 9.4 + bdr: PostgreSQL 9.4.4 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.7.2-5) 4.7.2, 64-bit kernel version: 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1 x86_64 GNU/Linux This is consolidation databases, in this machine there are around 250+ wal sender processes.

Re: [GENERAL] Checkpoint write time - anything unusual?

pinker wrote: > I've just run pgBadger on my pg logs and wonder if those checkpoint > statistics is something I should worry about or not? > The highest write time is about 47 minutes but I'm not sure if that's > checkpoint_completion_target*checkpoint_target value or real time between > sending