设为首页 收藏本站
查看: 665|回复: 0

[经验分享] postgresql pg_buffercache

[复制链接]

尚未签到

发表于 2016-11-19 09:11:47 | 显示全部楼层 |阅读模式
pg_buffercache模块是用于查看shared buffer cache信息,决定shared buffer cache大还是小。
Installing pg_buffercache into a database:
$ createdb pgbench
$ psql -d pgbench -f /usr/share/postgresql/contrib/pg_buffercache.sql
两步即可完成
pg_buffercache.sql内容:
/* contrib/pg_buffercache/pg_buffercache--1.0.sql */
-- complain if script is sourced in psql, rather than via CREATE EXTENSION
\echo Use "CREATE EXTENSION pg_buffercache" to load this file. \quit
-- Register the function.
CREATE FUNCTION pg_buffercache_pages()
RETURNS SETOF RECORD
AS 'MODULE_PATHNAME', 'pg_buffercache_pages'
LANGUAGE C;
-- Create a view for convenient access.
CREATE VIEW pg_buffercache AS
SELECT P.* FROM pg_buffercache_pages() AS P
(bufferid integer, relfilenode oid, reltablespace oid, reldatabase oid,
relforknumber int2, relblocknumber int8, isdirty bool, usagecount int2);
-- Don't want these to be available to public.
REVOKE ALL ON FUNCTION pg_buffercache_pages() FROM PUBLIC;
REVOKE ALL ON pg_buffercache FROM PUBLIC;
创建函数和视图,回收PUBLIC 权限。

NameTypeReferencesDescriptionbufferidintegerID, in the range 1..shared_buffersrelfilenodeoidpg_class.relfilenodeFilenode number of the relationreltablespaceoidpg_tablespace.oidTablespace OID of the relationreldatabaseoidpg_database.oidDatabase OID of the relationrelblocknumberbigintPage number within the relationrelforknumbersmallintFork number within the relationisdirtybooleanIs the page dirty?usagecountsmallintPage LRU count
pg_buffercache使用:
查看shared buffers大小:
postgres=# SELECT name,setting,unit,current_setting(name) FROM pg_settings WHERE name='shared_buffers';
name | setting | unit | current_setting
----------------+---------+------+-----------------
shared_buffers | 4096 | 8kB | 32MB
(1 row)
postgres=# select count(*) from pg_buffercache;
count
-------
4096
(1 row)
可见block数量一致,大小一致。
查看当前数据库buffer的使用情况排名:
SELECT
c.relname,
count(*) AS buffers
FROM pg_class c
INNER JOIN pg_buffercache b
ON b.relfilenode=c.relfilenode
INNER JOIN pg_database d
ON (b.reldatabase=d.oid AND d.datname=current_database())
GROUP BY c.relname
ORDER BY 2 DESC
LIMIT 10;
relname | buffers
---------------------------+---------
pg_statistic | 15
pg_operator | 13
pg_depend_reference_index | 13
pg_depend | 13
pg_rewrite | 8
pg_depend_depender_index | 6
pg_toast_2619 | 6
pg_index | 6
pg_extension | 5
pg_namespace | 5
(10 rows)
使用pg_buffercache比较灵活,可以通过isdirty字段查询脏块,如果是未使用的buffer,那么除了bufferid,其他字段都为空值。
select count(*) from pg_buffercache where isdirty is true;
select count(*)*8/1024||'MB' from pg_buffercache where relfilenode is null and reltablespace is null and reldatabase is null and relforknumber is null and relblocknumber is null and isdirty is null and usagecount is null;
查看buffercache对象的使用大小以及百分比
SELECT
c.relname,
pg_size_pretty(count(*) * 8192) as buffered,
round(100.0 * count(*) /
(SELECT setting FROM pg_settings
WHERE name='shared_buffers')::integer,1)
AS buffers_percent,
round(100.0 * count(*) * 8192 /
pg_relation_size(c.oid),1)
AS percent_of_relation
FROM pg_class c
INNER JOIN pg_buffercache b
ON b.relfilenode = c.relfilenode
INNER JOIN pg_database d
ON (b.reldatabase = d.oid AND d.datname = current_database())
GROUP BY c.oid,c.relname
ORDER BY 3 DESC
LIMIT 10;


relname | buffered | buffers_percent | percent_of_relation
----------------------------------+----------+-----------------+---------------------
pg_statistic | 120 kB | 0.4 | 100.0
pg_depend | 104 kB | 0.3 | 29.5
pg_operator | 104 kB | 0.3 | 100.0
pg_depend_reference_index | 104 kB | 0.3 | 50.0
pg_rewrite | 64 kB | 0.2 | 66.7
pg_operator_oid_index | 32 kB | 0.1 | 100.0
pg_statistic_relid_att_inh_index | 32 kB | 0.1 | 100.0
pg_operator_oprname_l_r_n_index | 40 kB | 0.1 | 100.0
pg_depend_depender_index | 48 kB | 0.1 | 22.2
pg_amop_fam_strat_index | 32 kB | 0.1 | 100.0
缓冲区使用分布:
SELECT
c.relname, count(*) AS buffers,usagecount
FROM pg_class c
INNER JOIN pg_buffercache b
ON b.relfilenode = c.relfilenode
INNER JOIN pg_database d
ON (b.reldatabase = d.oid AND d.datname = current_database())
GROUP BY c.relname,usagecount
ORDER BY c.relname,usagecount;
relname | buffers | usagecount
-----------------------------------+---------+------------
pg_aggregate | 1 | 5
pg_aggregate_fnoid_index | 1 | 4
pg_aggregate_fnoid_index | 1 | 5
pg_am | 1 | 5
pg_amop | 3 | 5
pg_amop_fam_strat_index | 1 | 1
pg_amop_fam_strat_index | 3 | 5
pg_amop_opr_fam_index | 3 | 5
pg_amproc | 1 | 4
pg_amproc | 1 | 5
pg_amproc_fam_proc_index | 2 | 5
pg_attrdef | 1 | 3
pg_attrdef_adrelid_adnum_index | 2 | 3
pg_attrdef_oid_index | 1 | 1
pg_attrdef_oid_index | 1 | 2
pg_cast | 2 | 5
pg_cast_source_target_index | 2 | 5
pg_collation | 1 | 1
pg_collation_oid_index | 1 | 3
pg_collation_oid_index | 2 | 5
pg_constraint | 1 | 1
pg_default_acl_role_nsp_obj_index | 1 | 5
pg_depend | 3 | 1
pg_depend | 1 | 2
pg_depend | 9 | 5
pg_depend_depender_index | 1 | 4
pg_depend_depender_index | 5 | 5
pg_depend_reference_index | 2 | 1
pg_depend_reference_index | 1 | 2
pg_depend_reference_index | 1 | 4
pg_depend_reference_index | 9 | 5
太长这里截取部分。

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-302407-1-1.html 上篇帖子: PostgreSQL简介及下载 下篇帖子: postgresql streaming replication
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表