greenplum(gp)postgre清理pg_xlog释放空间
2024-05-14 20:34:52
greenplum(gp)/postgre清理pg_xlog释放空间
greenplum数据库在大量数据更新时，会产生大量的pg_xlog，造成磁盘空间占用；系统长时间运行后，pg_log文件夹下日志文件也会越来越大，合理的做法是日志文件的磁盘和数据目录挂载在不同的磁盘路径下或者磁盘扩容；若在同一路径下，可将日志文件备份到其他路径，腾出一部分空间，或清理pg_xlog
【注意】：
- pg_xlog下面的日志不能人为的随意删除，例如使用rm -rf命令，否则给数据库带来巨大灾难，服务启动失败
- greenplum/PostgreSQL自带了清理wal日志的工具叫pg_resetxlog，其实是通过重置xlog的值来清理xlog文件。但是这个工具通常不建议使用，在无法扩容且磁盘快满等特殊情况下，可以选择清理，但也会有一定几率造成服务启动异常。
- 一定不能在服务运行的情况下去操作pg_resetxlog
查看当前pg_xlog占用大小【gpmaster操作】
[gpadmin@gpmaster ~]$ cd /home/gpadmin/gpdata/gpmaster/gpseg-1/
[gpadmin@gpmaster gpseg-1]$ du -sh *
99M base
4.1M global
20K gpperfmon
4.0K gpsegconfig_dump
4.0K gpssh.conf
4.0K internal.auto.conf
36K pg_clog
36K pg_distributedlog
4.0K pg_dynshmem
8.0K pg_hba.conf
4.0K pg_ident.conf
28K pg_log
12K pg_logical
76K pg_multixact
36K pg_notify
4.0K pg_replslot
4.0K pg_serial
4.0K pg_snapshots
4.0K pg_stat
4.0K pg_stat_tmp
36K pg_subtrans
4.0K pg_tblspc
4.0K pg_twophase
4.0K pg_utilitymodedtmredo
4.0K PG_VERSION
193M pg_xlog
4.0K postgresql.auto.conf
24K postgresql.conf
4.0K postmaster.opts
4.0K postmaster.pid
可以看到当前数据目录下pg_xlog 193M大小
实际上集群的每个数据存储节点上都会存在pg_xlog的空间占用
通过gpstate命令查看所有的数据存储路径【gpmaster操作】
[gpadmin@gpmaster gpdata]$ gpstate -s | grep -E "Master data directory|Datadir"|awk -F"=" '{print $2}'/home/gpadmin/gpdata/gpmaster/gpseg-1/home/gpadmin/gpdata/gpdatap1/gpseg0/home/gpadmin/gpdata/gpdatap2/gpseg1/home/gpadmin/gpdata/gpdatap1/gpseg2/home/gpadmin/gpdata/gpdatap2/gpseg3/home/gpadmin/gpdata/gpdatap1/gpseg4/home/gpadmin/gpdata/gpdatap2/gpseg5
这里获取到的路径清单即为集群所有节点的数据存储目录，其中gpstandby路径和gpmaster一样
停止gp集群服务【gpmaster操作】
[gpadmin@gpmaster gpdata]$ gpstop
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:---------------------------------------------
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:-Segment instances that will be shutdown:
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:---------------------------------------------
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:- Host Datadir Port Status
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:- segment01 /home/gpadmin/gpdata/gpdatap1/gpseg0 6000 u
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:- segment01 /home/gpadmin/gpdata/gpdatap2/gpseg1 6001 u
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:- segment02 /home/gpadmin/gpdata/gpdatap1/gpseg2 6000 u
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:- segment02 /home/gpadmin/gpdata/gpdatap2/gpseg3 6001 u
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:- segment03 /home/gpadmin/gpdata/gpdatap1/gpseg4 6000 u
20220630:16:19:37:005122 gpstop:gpmaster:gpadmin-[INFO]:- segment03 /home/gpadmin/gpdata/gpdatap2/gpseg5 6001 uContinue with Greenplum instance shutdown Yy|Nn (default=N):
> y
20220630:16:19:39:005122 gpstop:gpmaster:gpadmin-[INFO]:-Commencing Master instance shutdown with mode='smart'
20220630:16:19:39:005122 gpstop:gpmaster:gpadmin-[INFO]:-Master segment instance directory=/home/gpadmin/gpdata/gpmaster/gpseg-1
20220630:16:19:39:005122 gpstop:gpmaster:gpadmin-[INFO]:-Stopping master segment and waiting for user connections to finish ...
server shutting down
20220630:16:19:40:005122 gpstop:gpmaster:gpadmin-[INFO]:-Cleaning up leftover gpsmon processes
20220630:16:19:40:005122 gpstop:gpmaster:gpadmin-[INFO]:-No leftover gpsmon processes on some hosts. not attempting forceful termination on these hosts
20220630:16:19:40:005122 gpstop:gpmaster:gpadmin-[INFO]:-Cleaning up leftover shared memory
[gpadmin@gpmaster gpdata]$ 清理流程【gpmaster操作】
# 注意操作用户均为gpadmin管理员用户来操作，其他linux普通用户无法操作
# pg_controldata命令读取的pg_control里存储路径的元数据信息
[gpadmin@gpmaster gpseg-1]$ pg_controldata /home/gpadmin/gpdata/gpmaster/gpseg-1 | grep -E "Latest checkpoint's NextXID|Latest checkpoint's NextOID"
Latest checkpoint's NextXID: 0/735
Latest checkpoint's NextOID: 16395# -o 参数为查询到的NextOID，-x 参数为查询到的NextXID，-f 参数为对应的数据存储目录
[gpadmin@gpmaster gpseg-1]$ pg_resetxlog -o 16395 -x 735 -f /home/gpadmin/gpdata/gpmaster/gpseg-1
WARNING: Do not use this on Greenplum. pg_resetxlog might cause data loss
and render system irrecoverable. Do you wish to proceed? [yes/no] yes
Transaction log reset
[gpadmin@gpmaster gpseg-1]$ 再次验证数据存储目录【gpmaster操作】
[gpadmin@gpmaster gpseg-1]$ du -sh *
99M base
4.1M global
20K gpperfmon
4.0K gpsegconfig_dump
4.0K gpssh.conf
4.0K internal.auto.conf
36K pg_clog
36K pg_distributedlog
4.0K pg_dynshmem
8.0K pg_hba.conf
4.0K pg_ident.conf
36K pg_log
12K pg_logical
76K pg_multixact
36K pg_notify
4.0K pg_replslot
4.0K pg_serial
4.0K pg_snapshots
52K pg_stat
4.0K pg_stat_tmp
36K pg_subtrans
4.0K pg_tblspc
4.0K pg_twophase
4.0K pg_utilitymodedtmredo
4.0K PG_VERSION
65M pg_xlog
4.0K postgresql.auto.conf
24K postgresql.conf
4.0K postmaster.opts可以看到当前数据目录下pg_xlog 65M大小，已经被清理
同样操作方式逐个节点实施清理【根据机器清单逐个执行】
【注意】:
- 涉及的数据路径均以真实环境查询到的数据存储路径清单为准
- NextXID和NextOID均以真实环境查询到的结果为准
# 【gpstandby操作】
[gpadmin@gpstandby gpdata]$ pg_controldata /home/gpadmin/gpdata/gpmaster/gpseg-1 | grep -E "Latest checkpoint's NextXID|Latest checkpoint's NextOID"
Latest checkpoint's NextXID: 0/735
Latest checkpoint's NextOID: 16395
[gpadmin@gpstandby gpdata]$
[gpadmin@gpstandby gpdata]$ pg_resetxlog -o 16395 -x 735 -f /home/gpadmin/gpdata/gpmaster/gpseg-1
WARNING: Do not use this on Greenplum. pg_resetxlog might cause data loss
and render system irrecoverable. Do you wish to proceed? [yes/no] yes
Transaction log reset
[gpadmin@gpstandby gpdata]$ # 【segment01操作】
[gpadmin@segment01 gpseg0]$ pg_controldata /home/gpadmin/gpdata/gpdatap1/gpseg0 | grep -E "Latest checkpoint's NextXID|Latest checkpoint's NextOID"
Latest checkpoint's NextXID: 0/726
Latest checkpoint's NextOID: 16392
[gpadmin@segment01 gpseg0]$ pg_controldata /home/gpadmin/gpdata/gpdatap2/gpseg1 | grep -E "Latest checkpoint's NextXID|Latest checkpoint's NextOID"
Latest checkpoint's NextXID: 0/726
Latest checkpoint's NextOID: 16392
[gpadmin@segment01 gpseg0]$
[gpadmin@segment01 gpseg0]$
[gpadmin@segment01 gpseg0]$ pg_resetxlog -o 16392 -x 726 -f /home/gpadmin/gpdata/gpdatap1/gpseg0
WARNING: Do not use this on Greenplum. pg_resetxlog might cause data loss
and render system irrecoverable. Do you wish to proceed? [yes/no] yes
Transaction log reset
[gpadmin@segment01 gpseg0]$ pg_resetxlog -o 16392 -x 726 -f /home/gpadmin/gpdata/gpdatap2/gpseg1
WARNING: Do not use this on Greenplum. pg_resetxlog might cause data loss
and render system irrecoverable. Do you wish to proceed? [yes/no] yes
Transaction log reset# 【segment02操作】
[gpadmin@segment02 gpdata]$ pg_controldata /home/gpadmin/gpdata/gpdatap1/gpseg2 | grep -E "Latest checkpoint's NextXID|Latest checkpoint's NextOID"
Latest checkpoint's NextXID: 0/726
Latest checkpoint's NextOID: 16392
[gpadmin@segment02 gpdata]$ pg_controldata /home/gpadmin/gpdata/gpdatap2/gpseg3 | grep -E "Latest checkpoint's NextXID|Latest checkpoint's NextOID"
Latest checkpoint's NextXID: 0/726
Latest checkpoint's NextOID: 16392
[gpadmin@segment02 gpdata]$
[gpadmin@segment02 gpdata]$ pg_resetxlog -o 16392 -x 726 -f /home/gpadmin/gpdata/gpdatap1/gpseg2
WARNING: Do not use this on Greenplum. pg_resetxlog might cause data loss
and render system irrecoverable. Do you wish to proceed? [yes/no] yes
Transaction log reset
[gpadmin@segment02 gpdata]$ pg_resetxlog -o 16392 -x 726 -f /home/gpadmin/gpdata/gpdatap2/gpseg3
WARNING: Do not use this on Greenplum. pg_resetxlog might cause data loss
and render system irrecoverable. Do you wish to proceed? [yes/no] yes
Transaction log reset# 【segment03操作】
[gpadmin@segment03 ~]$ pg_controldata /home/gpadmin/gpdata/gpdatap1/gpseg4 | grep -E "Latest checkpoint's NextXID|Latest checkpoint's NextOID"
Latest checkpoint's NextXID: 0/726
Latest checkpoint's NextOID: 16392
[gpadmin@segment03 ~]$ pg_controldata /home/gpadmin/gpdata/gpdatap2/gpseg5 | grep -E "Latest checkpoint's NextXID|Latest checkpoint's NextOID"
Latest checkpoint's NextXID: 0/726
Latest checkpoint's NextOID: 16392
[gpadmin@segment03 ~]$
[gpadmin@segment03 ~]$ pg_resetxlog -o 16392 -x 726 -f /home/gpadmin/gpdata/gpdatap1/gpseg4
WARNING: Do not use this on Greenplum. pg_resetxlog might cause data loss
and render system irrecoverable. Do you wish to proceed? [yes/no] yes
Transaction log reset
[gpadmin@segment03 ~]$ pg_resetxlog -o 16392 -x 726 -f /home/gpadmin/gpdata/gpdatap2/gpseg5
WARNING: Do not use this on Greenplum. pg_resetxlog might cause data loss
and render system irrecoverable. Do you wish to proceed? [yes/no] yes
Transaction log reset截止到这，整个集群各节点的数据目录的pg_xlog已经清理完毕
启动gp集群服务【gpmaster操作】
# 启动gp集群
[gpadmin@gpmaster gpdata]$ gpstart
20220630:16:48:34:006792 gpstart:gpmaster:gpadmin-[INFO]:-Starting gpstart with args:
20220630:16:48:34:006792 gpstart:gpmaster:gpadmin-[INFO]:-Gathering information and validating the environment...
20220630:16:48:35:006792 gpstart:gpmaster:gpadmin-[INFO]:- Host Datadir Port
20220630:16:48:35:006792 gpstart:gpmaster:gpadmin-[INFO]:- segment01 /home/gpadmin/gpdata/gpdatap1/gpseg0 6000
20220630:16:48:35:006792 gpstart:gpmaster:gpadmin-[INFO]:- segment01 /home/gpadmin/gpdata/gpdatap2/gpseg1 6001
20220630:16:48:35:006792 gpstart:gpmaster:gpadmin-[INFO]:- segment02 /home/gpadmin/gpdata/gpdatap1/gpseg2 6000
20220630:16:48:35:006792 gpstart:gpmaster:gpadmin-[INFO]:- segment02 /home/gpadmin/gpdata/gpdatap2/gpseg3 6001
20220630:16:48:35:006792 gpstart:gpmaster:gpadmin-[INFO]:- segment03 /home/gpadmin/gpdata/gpdatap1/gpseg4 6000
20220630:16:48:35:006792 gpstart:gpmaster:gpadmin-[INFO]:- segment03 /home/gpadmin/gpdata/gpdatap2/gpseg5 6001Continue with Greenplum instance startup Yy|Nn (default=N):
> y
20220630:16:48:37:006792 gpstart:gpmaster:gpadmin-[INFO]:-Commencing parallel segment instance startup, please wait...
20220630:16:48:37:006792 gpstart:gpmaster:gpadmin-[INFO]:-Checking if standby master is running on host: gpstandby in directory: /home/gpadmin/gpdata/gpmaster/gpseg-1
20220630:16:48:38:006792 gpstart:gpmaster:gpadmin-[INFO]:-Database successfully started# 查看集群运行状态
[gpadmin@gpmaster gpseg-1]$ gpstate
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-Starting gpstate with args:
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 6.19.0 build commit:c88801925e5d51e4be57f54ff2158ed74a264b8e Open Source'
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 9.4.26 (Greenplum Database 6.19.0 build commit:c88801925e5d51e4be57f54ff2158ed74a264b8e Open Source) on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 6.4.0, 64-bit compiled on Dec 8 2021 23:08:44'
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-Obtaining Segment details from master...
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-Gathering data from segments...
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-Greenplum instance status summary
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-----------------------------------------------------
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Master instance = Active
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Master standby = gpstandby
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Standby master state = Standby host passive
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total segment instance count from metadata = 6
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-----------------------------------------------------
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Primary Segment Status
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-----------------------------------------------------
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total primary segments = 6
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total primary segment valid (at master) = 6
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total primary segment failures (at master) = 0
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total number of postmaster.pid files missing = 0
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total number of postmaster.pid files found = 6
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total number of postmaster.pid PIDs missing = 0
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total number of postmaster.pid PIDs found = 6
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total number of /tmp lock files missing = 0
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total number of /tmp lock files found = 6
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total number postmaster processes missing = 0
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Total number postmaster processes found = 6
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-----------------------------------------------------
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Mirror Segment Status
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-----------------------------------------------------
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:- Mirrors not configured on this array
20220630:17:20:19:007703 gpstate:gpmaster:gpadmin-[INFO]:-----------------------------------------------------
# 登录数据库
[gpadmin@gpmaster gpseg-1]$ psql
psql (9.4.26)
Type "help" for help.testdb=#
testdb=# \dList of relationsSchema | Name | Type | Owner | Storage
--------+----------------------+-------+---------+---------public | amr_n042_company_inv | table | gpadmin | heap
(1 row)testdb=#
testdb=# select * from amr_n042_company_inv limit 1;rec_id | eid | inv | pid | eid_inv | inv_type | blic_type | blic_no | country | currency | sub_conam | acc
_conam | sub_conam_usd | acc_conam_usd | con_prop | con_form | con_date | created | update_time | delete_flg
----------------------------------+----------------------------------+------------------+----------------------------------+---------+----------+-----------+---------+---------+----------+-----------+----------
-------------+----------------------+----------------------+------------------------+----------+------------+---------------------+---------------------+------------95e6834d0a3d99e9ea8811855ae9229d | f1a385984a2b3860624906202b84cfe1 | 测试数据测试数据 | 67f87ebe99ad9e6c21abeae9482ab52d | | 20 | | | 156 | 156 | 50.000000 | 50.000000
000000000000 | 7.370000000000000000 | 7.370000000000000000 | 100.000000000000000000 | | 2017-05-31 | 2020-11-23 15:14:59 | 2022-02-12 08:07:48 | 0
(1 row)集群运行一切正常，清理流程至此实施完毕
执行数据库导入数据任务报错
WARNING: database with OID 0 must be vacuumed within 147483647 transactions (seg1 192.168.0.243:6001 pid=7269)
testdb=# \timing
Timing is on.
testdb=# \i amr_n042_company_modify.sql
SET
Time: 5.479 msset_config
------------(1 row)Time: 9.566 ms
SET
Time: 0.337 ms
SET
Time: 0.277 ms
SET
Time: 0.260 ms
SET
Time: 0.257 ms
SET
Time: 0.246 ms
psql:amr_n042_company_modify.sql:36: WARNING: database with OID 0 must be vacuumed within 147483647 transactions
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
psql:amr_n042_company_modify.sql:36: WARNING: database with OID 0 must be vacuumed within 147483647 transactions (seg2 192.168.0.98:6000 pid=7305)
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
psql:amr_n042_company_modify.sql:36: WARNING: database with OID 0 must be vacuumed within 147483647 transactions (seg3 192.168.0.98:6001 pid=7306)
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
psql:amr_n042_company_modify.sql:36: WARNING: database with OID 0 must be vacuumed within 147483647 transactions (seg0 192.168.0.243:6000 pid=7270)
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
psql:amr_n042_company_modify.sql:36: WARNING: database with OID 0 must be vacuumed within 147483647 transactions (seg1 192.168.0.243:6001 pid=7269)
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
psql:amr_n042_company_modify.sql:36: WARNING: database with OID 0 must be vacuumed within 147483647 transactions (seg5 192.168.0.156:6001 pid=12038)
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
psql:amr_n042_company_modify.sql:36: WARNING: database with OID 0 must be vacuumed within 147483647 transactions (seg4 192.168.0.156:6000 pid=12037)
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
CREATE TABLE
Time: 85.925 ms
psql:amr_n042_company_modify.sql:39: WARNING: database with OID 0 must be vacuumed within 147483646 transactions
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
发现本次清理pg_xlog后，在数据库写入数据时，报了大量的WARNING警告
WARNING: database with OID 0 must be vacuumed within 147483647 transactions (seg1 192.168.0.243:6001 pid=7269)
HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
处理办法
【注意】：这里的数据库是根据自己真实场景的数据库名称来执行 VACUUM FREEZE
# 执行vacuum freeze操作
[gpadmin@gpmaster ~]$ nohup psql -c " VACUUM FREEZE " testdb 2>&1 &[gpadmin@gpmaster ~]$ nohup psql -c " VACUUM FREEZE " postgres 2>&1 &
# 耐心等待需要使用的database库逐个执行完VACUUM FREEZE
vacuum freeze 命令表示强制对表或数据库进行freeze 操作。freeze 操作是为了保证整个数据库的最老最新事务差不能超过20亿，从而防止事务ID 发生回卷
在PostgreSQL 中，XID 是用32位无符号数来表示的，很容易发生溢出的情况，造成事务可见性混乱
再次登录数据库执行\i amr_n042_company_modify.sql导入数据时发现不再有告警提示了。
greenplum(gp)postgre清理pg_xlog释放空间相关推荐
- 云服务器如何清理垃圾释放空间？
1.清除安装文件 及时删除没有实际用处的安装文件可以节省出许多空间容量. 2.清除数据库垃圾 服务器数据库会产生死链等垃圾信息,这些垃圾信息不及时清理,会逐渐占据数据库容量,使得服务器访问速度越来越慢 ...
- 计算机主机清理步骤,三个方法教你如何正确清理C盘空间
原标题:三个方法教你如何正确清理C盘空间 Windows电脑操作系统一般都是安装在磁盘驱动器的C盘中,一旦运行,变会产生许多垃圾文件,C盘空间在一定的程度上都会越来越小.伴随着电脑工作的时间越久,C盘 ...
- linux清理磁盘空间的脚本,在Ubuntu和Linux Mint上释放空间的7种简单方法
Linux系统空间不足?您可以通过以下几种方式清理系统,释放Ubuntu和其他基于Ubuntu的Linux发行版上的空间. 随着时间的流逝,随着添加和删除程序,任何操作系统都可能变得混乱.如果您拥有T ...
- 怎么释放C盘空间？清理C盘空间的4大方法分享！
案例:怎么释放c盘空间 [朋友们,最近我的c盘空间内存严重不足了,想释放一下c盘的空间,大家有什么好的方法吗?] 在使用电脑的过程中,经常会遇到C盘空间不足的问题,这时候就需要释放C盘的空间.但是,很 ...
- Mac内存空间不足如何释放储存空间?深度清理Mac磁盘空间的方法教程
今日coco玛奇朵将分享一些能够释放大量Mac内存空间的方法,以便大家能够优化Mac的运行速度外还能规避由于Mac空间不足而导致安装Ventura时出现的一系列问题. 大家都知道更新Macos都需要预 ...
- 三、Win10系统怎么自动清理缓存，无需手动按时清理磁盘，自动释放空间哦
开启自动清理后,Windows可以通过删除不需要的文件(例如临时文件和回收站中的内容)自动释放空间,小伙伴们也不用每次都来手动清理啦! 开启方法 1.依次点击[开始]-[设置]-[系统]. 2.选择[ ...
- oracle+怎么清理碎片,oracle 收缩表、清理碎片，释放空间
可以用来收缩段,消除空间碎片的方法有两种: 1.alter table table_name move 需要注意: 1)move操作会锁表.(如果是很小的表,可以在线做.如果是大表一定要注意,会长时间 ...
- mysql 表空间收缩_mysql表碎片清理和表空间收缩
mysql表碎片清理和表空间收缩(即清理碎片后report_site_day.ibd文件磁盘空间减小,该方案基于独立表空间存储方式) OPTIMIZETABLE [tablename],当然这种方式只 ...
- Oracle 扩展sysaux,oracle 清理SYSAUX表空间
简介 oracle 清理SYSAUX表空间 处理思路 1.查询表空间使用情况1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17SELECT UPPER(F.TABLES ...
- 群晖NAS删除文件不释放空间的原因和方法
1.删除了文件没清理回收站 控制面板-系统-计划任务-新增计划任务-回收站 默认就行,每天0点自动清理.或直接手动清理即可. 2.同步软件版本控制一般设置5即可,有些同步软件即使删除了原文件和清空了回 ...
最新文章
- java读书心得_Java读书笔记 20100815
- 业务代码中，太多 if else 怎么办？
- dedeampz mysql启动不了_localhost打不开？dedeampz环境启动不了？本地php环境启动失败？...
- rmmod 提示 No such file or directory
- 项目经理沟通的四个好习惯
- java基础之多线程笔记
- JSP变量和方法声明
- 曲率曲线JAVA_DEM曲率计算
- win10恢复经典开始菜单_打造个性化开始菜单，Win10 开始菜单任务栏美化增强软件...
- 五、文章详情页制作及跳转功能实现《iVX低代码/无代码个人博客制作》
- 投资投机经典著作55本
- iOS面试与核心基础之启动优化
- android台式电脑系统安装,怎么在台式机上安装安卓系统
- 如何显示电脑已连接的WiFi的密码
- 高并发限流-漏桶算法和令牌桶算法
- 深入浅出Zookeeper集群搭建
- python 图片锐化_Python图像处理介绍--图像模糊与锐化
- 有一种数叫回文数，正读和反读都一样，如12321便是一个回文数。编写一个程序，从命令行得到一个整数，判断该数是不是回文数。
- Excel学习笔记-图表(双向条形图、甘特图、饼图、往PPT中插入图表)
- 云服务器怎样杀毒软件,如何在云服务器里面安装杀毒软件？安装杀毒软件的好处...