pgsql: Match the buffer usage tracking for leader and worker backends.

2018-08-02 Thread Amit Kapila
Match the buffer usage tracking for leader and worker backends. In the leader backend, we don't track the buffer usage for ExecutorStart phase whereas in worker backend we track it for ExecutorStart phase as well. This leads to different value for buffer usage stats for the parallel and non-paral

pgsql: Match the buffer usage tracking for leader and worker backends.

2018-08-02 Thread Amit Kapila
Match the buffer usage tracking for leader and worker backends. In the leader backend, we don't track the buffer usage for ExecutorStart phase whereas in worker backend we track it for ExecutorStart phase as well. This leads to different value for buffer usage stats for the parallel and non-paral

pgsql: Match the buffer usage tracking for leader and worker backends.

2018-08-02 Thread Amit Kapila
Match the buffer usage tracking for leader and worker backends. In the leader backend, we don't track the buffer usage for ExecutorStart phase whereas in worker backend we track it for ExecutorStart phase as well. This leads to different value for buffer usage stats for the parallel and non-paral

pgsql: Match the buffer usage tracking for leader and worker backends.

2018-08-02 Thread Amit Kapila
Match the buffer usage tracking for leader and worker backends. In the leader backend, we don't track the buffer usage for ExecutorStart phase whereas in worker backend we track it for ExecutorStart phase as well. This leads to different value for buffer usage stats for the parallel and non-paral