问候， 我有一个恼人的问题。我目前在Linux（x86）上运行PostgreSQL-7.3.4 。此问题始于7.3.3。我有一个更大的数据库 （大约3GB转储）。我运行vacuumdb -z -a -f每天三次通过cronjob虔诚地。 上个月突然（大约3年后）我开始得到 当vacuumdb运行时这个警告： 信息：索引pg_largeobject_loid_pn_index：第903页;元组323847： 删除0. CPU 0.04s / 0.07u秒经过0.10秒 警告：索引pg_largeobject_loid_pn_index：索引数量''tUPLES （323847）不是和HEAP一样'（323802）。 重新创建索引。 所以我把postgresql放到独立模式，重新创建索引，以及 一切都好了大约2天，然后问题就会恢复。 我做了一些谷歌搜索，发现这是一个潜在的错误 版本的postgresql，但据说固定在7.3.4及更高版本 版本。所以我升级到7.3.4（使用 postgresql ftp服务器上的半官方RPM）。掉进了独立模式，重新编制索引， ，过去一个月一切都很好。 直到今天早上再次回来。运行这个运行的服务器没有任何硬件问题，没有关闭 不正确或类似的东西。它目前的正常运行时间为209天，并且 postgresql从未正常关机。 现在我愿意进一步升级，但我真的可以'买不起 不必要的停机时间。所以我想要一些指导/输入 版本的postgresql不会有这个bug。或许这根本不是 的错误，还有其他一些奇怪的问题？ 无论哪种方式，任何和所有建议都是赞赏。 谢谢！ Lonni ------------- --------------（广播结束）--------------------------- 提示3：如果通过Usenet发布/阅读，请发送适当的 subscribe-nomail命令到 ma ******* @ postgresql 以便您的 消息可以干净地通过邮件列表
Greetings, I''ve got an annoying problem. I''m currently running PostgreSQL-7.3.4 on Linux (x86). This problem started with 7.3.3. I''ve got a database that is on the larger side (about 3GB dump). I run "vacuumdb -z -a -f" religiously via a cronjob three times a day. All of a sudden last month (after about 3 years) I started getting this warning when vacuumdb was run: INFO: Index pg_largeobject_loid_pn_index: Pages 903; Tuples 323847: Deleted 0. CPU 0.04s/0.07u sec elapsed 0.10 sec. WARNING: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX'' TUPLES (323847) IS NOT THE SAME AS HEAP'' (323802). Recreate the index. So I put postgresql into standalone mode, recreated the index, and everything was ok for about 2 days, and then the problem would return. I did some Googling and found that this was a potential bug in older versions of postgresql, but was supposedly fixed in 7.3.4 and later versions. So I upgraded to 7.3.4 (using the semi-official RPMs on the postgresql ftp servers). Dropped into standalone mode, reindexed, and everything was fine for about the past month. Until this morning when it came back again. The server where this is running isn''t having any hardware problems, isn''t getting shutdown improperly or anything like that. Its current uptime is 209 days, and postgresql is never shutdown improperly. Now I''d be willing to upgrade further, but I really can''t afford unnecessary downtime. So I''d like some guidance/input on which version of postgresql will not have this bug. Or maybe this isn''t the bug at all, and there''s some other weird problem? Either way, any and all advice is appreciated. Thanks! Lonni ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to ma*******@postgresql so that your message can get through to the mailing list cleanly
推荐答案Lonni Friedman< ne ****** @ gmail>写道： Lonni Friedman <ne******@gmail> writes: 上个月突然（大约3年后）我在vacuumdb运行时开始收到这个警告： INFO：索引pg_largeobject_loid_pn_index：第903页;元组323847：已删除0. CPU 0.04s / 0.07u秒已过0.10秒。警告：索引pg_largeobject_loid_pn_index：索引数量的数量（323847）不是同样的问题' '（323802）。重新创建索引。 All of a sudden last month (after about 3 years) I started getting this warning when vacuumdb was run: INFO: Index pg_largeobject_loid_pn_index: Pages 903; Tuples 323847: Deleted 0. CPU 0.04s/0.07u sec elapsed 0.10 sec. WARNING: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX'' TUPLES (323847) IS NOT THE SAME AS HEAP'' (323802). Recreate the index.
嗯。是不是总是那个索引，或者你在其他索引上看过这个吗？ 我不知道7.3。*中的任何已知错误可能导致这种 错误。不要以为你对如何重现这个问题有什么建议吗？ 问候，汤姆小巷 ---------------------------（广播结束）---------------- ----------- 提示3：如果通过Usenet发布/阅读，请发送适当的 subscribe-nomail命令给 ma ******* @ postgresql 以便您的 消息可以通过干净的邮件清单
Hmm. Is it always that same index, or have you seen this on other indexes? I''m not aware of any known bug in 7.3.* that could lead to this sort of error. Don''t suppose you have any suggestions about how to reproduce the problem? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to ma*******@postgresql so that your message can get through to the mailing list cleanly
Lonni Friedman< ne ****** @ gmail>写道： Lonni Friedman <ne******@gmail> writes: 上个月突然（大约3年后）我在vacuumdb运行时开始收到这个警告： INFO：索引pg_largeobject_loid_pn_index：第903页;元组323847：已删除0. CPU 0.04s / 0.07u秒已过0.10秒。警告：索引pg_largeobject_loid_pn_index：索引数量的数量（323847）不是同样的问题' '（323802）。重新创建索引。 All of a sudden last month (after about 3 years) I started getting this warning when vacuumdb was run: INFO: Index pg_largeobject_loid_pn_index: Pages 903; Tuples 323847: Deleted 0. CPU 0.04s/0.07u sec elapsed 0.10 sec. WARNING: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX'' TUPLES (323847) IS NOT THE SAME AS HEAP'' (323802). Recreate the index.
嗯。是不是总是那个索引，或者你在其他索引上看过这个吗？ 我不知道7.3。*中的任何已知错误可能导致这种 错误。不要以为你对如何重现这个问题有什么建议吗？ 问候，汤姆小巷 ---------------------------（广播结束）---------------- ----------- 提示3：如果通过Usenet发布/阅读，请发送适当的 subscribe-nomail命令给 ma ******* @ postgresql 以便您的 消息可以通过干净的邮件清单
Hmm. Is it always that same index, or have you seen this on other indexes? I''m not aware of any known bug in 7.3.* that could lead to this sort of error. Don''t suppose you have any suggestions about how to reproduce the problem? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to ma*******@postgresql so that your message can get through to the mailing list cleanly
Lonni Friedman< ne ****** @ gmail>写道： Lonni Friedman <ne******@gmail> writes: 不幸的是，我不知道如何复制这个。在我从7.3.3升级到7.3.4（就像每次vacuumdb运行一样）之前，它发生得非常一致。 然后在转到7.3.4之后一个月没什么，现在它发生了每个vacuumdb再次运行。 Unfortunately, i have no clue how to replicate this. It was happening fairly consistantly before i upgraded from 7.3.3 to 7.3.4 (like nearly every vacuumdb run). Then nothing for a month after going to 7.3.4, and now its happening every vacuumdb run again.
一旦投诉开始出现，我希望它能继续下去，直到你重新索引指数。 问候，汤姆小巷 ---------------------------（广播结束）----------------- ---------- 提示2：您可以使用取消注册命令一次性取消所有列表 （发送取消注册YourEmailAddressHere到 ma ******* @ postgresql ）
Once the complaint starts appearing, I''d expect it to continue until you reindex the index. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to ma*******@postgresql)
更多推荐
vacuumdb失败,索引数量不同,而不是一样
发布评论