<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>惜分飞 &#187; postgres恢复</title>
	<atom:link href="https://www.xifenfei.com/tag/postgres%e6%81%a2%e5%a4%8d/feed" rel="self" type="application/rss+xml" />
	<link>https://www.xifenfei.com</link>
	<description>提供7*24专业数据库(Oracle,SQL Server,MySQL,PostgreSQL等)恢复和技术支持@Tel:17813235971</description>
	<lastBuildDate>Thu, 29 Oct 2026 15:31:46 +0000</lastBuildDate>
	<language>zh-CN</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>由于空间满导致PostgreSQL数据库异常处理</title>
		<link>https://www.xifenfei.com/2025/07/no-space-left-on-device-postgresql.html</link>
		<comments>https://www.xifenfei.com/2025/07/no-space-left-on-device-postgresql.html#comments</comments>
		<pubDate>Tue, 29 Jul 2025 15:36:09 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[PostgreSQL恢复]]></category>
		<category><![CDATA[pg异常处理]]></category>
		<category><![CDATA[pg恢复支持]]></category>
		<category><![CDATA[postgres恢复]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=11562</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2025/07/no-space-left-on-device-postgresql.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2025/07/no-space-left-on-device-postgresql.html" target="_blank">由于空间满导致PostgreSQL数据库异常处理</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>朋友和我反馈pg库异常,通过查看日志确认最初故障是由于磁盘空间满，导出出现类似:无法扩展文件 &#8220;pg_tblspc/16394/PG_13_202007201/16395/5055912.143&#8243;: No space left on device错误</p>
<pre class="brush: bash; title: ; notranslate">
2025-07-28 09:06:02.703 HKT [15352] 错误:  无法扩展文件 &quot;pg_tblspc/16394/PG_13_202007201/16395/5055912.143&quot;: No space left on device
2025-07-28 09:06:02.703 HKT [15352] 提示:  检查空闲磁盘控件.
2025-07-28 09:06:02.703 HKT [15352] 语句:  insert into 语句
2025-07-28 09:06:02.703 HKT [576] 错误:  无法扩展文件 &quot;pg_tblspc/16394/PG_13_202007201/16395/4477723.73&quot;: No space left on device
2025-07-28 09:06:02.703 HKT [576] 提示:  检查空闲磁盘控件.
2025-07-28 09:06:02.703 HKT [576] 语句:  update 语句
2025-07-28 09:06:02.706 HKT [11940] 错误:  无法扩展文件 &quot;pg_tblspc/16394/PG_13_202007201/16395/5055912.143&quot;: No space left on device
2025-07-28 09:06:02.706 HKT [11940] 提示:  检查空闲磁盘控件.
2025-07-28 09:06:02.706 HKT [11940] 语句:  insert into 语句
</pre>
<p><a href="https://www.xifenfei.com/wp-content/uploads/2025/07/pg-nofree.png"><img src="https://www.xifenfei.com/wp-content/uploads/2025/07/pg-nofree.png" alt="pg-nofree" width="846" height="481" class="alignleft size-full wp-image-11563" /></a><br />
<hr />
后续对d盘空间进行了清理,pg报无法打开文件&#8221;pg_tblspc/16394/PG_13_202007201/16395/4477706.16&#8243;(目标数据块5544906): Permission denied</p>
<pre class="brush: bash; title: ; notranslate">
2025-07-28 10:53:10.435 HKT [11920] 语句:  insert into语句
2025-07-28 10:53:10.435 HKT [18300] 错误:  无法打开文件&quot;pg_tblspc/16394/PG_13_202007201/16395/4477706.16&quot;(目标数据块5544906): Permission denied
</pre>
<p>和报:警告:  无法写入pg_tblspc/16394/PG_13_202007201/16395/4477706的块5545387错误</p>
<pre class="brush: bash; title: ; notranslate">
2025-07-28 11:05:11.008 HKT [5380] 警告:  无法写入pg_tblspc/16394/PG_13_202007201/16395/4477706的块5545387
2025-07-28 11:05:11.008 HKT [5380] 详细信息:  多次失败 --- 写错误可能是永久性的
2025-07-28 11:05:11.015 HKT [12072] 错误:  无法打开文件&quot;pg_tblspc/16394/PG_13_202007201/16395/4477706.17&quot;（目标块5545398）：上一段只有952个块
2025-07-28 11:05:11.015 HKT [12072] 上下文:  写入关系pg_tblspc/16394/PG_13_202007201/16395/4477706的块5545398
2025-07-28 11:05:11.015 HKT [12072] 语句:  select 语句
2025-07-28 11:05:11.016 HKT [12072] 警告:  无法写入pg_tblspc/16394/PG_13_202007201/16395/4477706的块5545398
2025-07-28 11:05:11.016 HKT [12072] 详细信息:  多次失败 --- 写错误可能是永久性的
</pre>
<p>查看4477706相关文件情况,初步看部分文件大小不对,结合上述报错,可以断定该表异常<br />
<a href="https://www.xifenfei.com/wp-content/uploads/2025/07/pgsize.png"><img src="https://www.xifenfei.com/wp-content/uploads/2025/07/pgsize.png" alt="pgsize" width="507" height="323" class="alignleft size-full wp-image-11564" /></a><br />
<hr />
通过查询pg字典确认该表具体名称</p>
<pre class="brush: sql; title: ; notranslate">
xifenfei=# select oid,relname,relnamespace from pg_class where  relfilenode=4477706;
  oid  |     relname      | relnamespace
-------+------------------+--------------
 16880 | xifenfei01_log   |         2200
(1 行记录)
</pre>
<p>尝试pg_dump导入数据报错：多次失败 &#8212; 写错误可能是永久性的</p>
<p>这次运气比较好,损坏的对象是一个日志表,可以直接清理掉,对该日志表进行清理,然后正常导出数据,如果遇到的损坏表是业务需要的表,可以使用pdu(<a href="https://www.xifenfei.com/2025/03/pdu-recovery-corrupt-block.html" title="PostgreSQL表文件损坏恢复—pdu恢复损坏的表文件" rel="noopener" target="_blank">PostgreSQL表文件损坏恢复—pdu恢复损坏的表文件</a>)进行恢复</p>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/12/sql-bak-0-lost-data.html" rel="bookmark" class="crp_title">模拟sql server故障备份完成恢复实现数据0丢失</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/10/linux7-8-single-user.html" rel="bookmark" class="crp_title">redhat系列7/8进入单用户模式</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/03/pg-delete-recovery.html" rel="bookmark" class="crp_title">pg误删除数据恢复（PostgreSQL delete数据恢复）</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/10/grubx64-efi-not-found.html" rel="bookmark" class="crp_title">Failed to open \EFI\redhat\grubx64.efi &#8211; Not Found 故障处理</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/01/ar8mswin1256.html" rel="bookmark" class="crp_title">中文环境显示AR8MSWIN1256（阿拉伯语字符集）</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/11/prvg-11975.html" rel="bookmark" class="crp_title">PRVG-11975 : The I/O scheduler parameter of device &#8220;/dev/sdm&#8221; did not match the expected value on nodes</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/09/delete-df-some-overwrit-recovery.html" rel="bookmark" class="crp_title">删除数据库文件并部分覆盖情况下Oracle恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/01/fio-disk-destruction-recovery.html" rel="bookmark" class="crp_title">fio测试io,导致磁盘文件系统损坏故障恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/12/ufs-recovery-lvm.html" rel="bookmark" class="crp_title">linux异常磁盘lvm恢复操作演示</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/04/sql-tempdb-error.html" rel="bookmark" class="crp_title">可能是 tempdb 空间用尽或某个系统表不一致故障处理</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/03/navicat-postgresql-datlastsysoid.html" rel="bookmark" class="crp_title">Navicat连接postgresql时出现column &#8220;datlastsysoid&#8221; does not exist错误解决</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/01/first-oracle-21c-recovery-ask.html" rel="bookmark" class="crp_title">第一例Oracle 21c恢复咨询</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2025/07/no-space-left-on-device-postgresql.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
