Re: [Patch] New pg_stat_tablespace view - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: [Patch] New pg_stat_tablespace view
Date
Msg-id CAN4CZFPf-VhzkXMsWjncXBVBc9vjw2tasJz99iN6MMCaMLna6g@mail.gmail.com
Whole thread Raw
In response to Re: [Patch] New pg_stat_tablespace view  (shihao zhong <zhong950419@gmail.com>)
Responses Re: [Patch] New pg_stat_tablespace view
List pgsql-hackers
Hello!

blk_read_time and blk_write_time doesn't seem to work, they show 0 to
me even after some workloads, and I don't see any assignments in the
code. The testcase also checks for "blk_read_time >= 0" which
trivially succeeds.

blocks_fetched is also misleading, it includes both reads and cache
hits. pg_stat_database calls this column blocks_read, and properly
substracts blocks_hit from it.

+ rel->pgstat_info->reltablespace = rel->rd_locator.spcOid;

Shouldn't this be included in TwoPhasePgStatRecord / pgstat_twophase_postcommit?



pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: pg_get__*_ddl consolidation
Next
From: Zsolt Parragi
Date:
Subject: Re: Add GoAway protocol message for graceful but fast server shutdown/switchover