mongo_fdw-问答-阿里云开发者社区-阿里云

开发者社区> 问答> 正文
阿里云
为了无法计算的价值
打开APP
阿里云APP内打开

mongo_fdw

2016-04-13 17:16:45 2640 1

我使用mongo_fdw 在PG 里面查询mongodb 数据,单独执行操作语句没问题,do $ declare begin ....end $$ 里面执行
select into var_x count(1) as count from "来自mongodb 的映射表" where xx=yy;
的时候,PG 就挂了(recovering 状态),实际上我在mongodb 里面的那张表只有200多条数据记录;PG 单独select * from from_mongodb_map_table; 没有问题的。
do $$ declare begin end$$ 代码,见插入的图片,只要执行到这里PG 就挂了。。crash

查看了一下PG日志:
2016-04-13 11:57:54.702 CST 18502 570b7c87.4846 1102 2016-04-11 18:29:27 CST 0 LOG 0 server process (PID 18582) was terminated by signal 6: Aborted "Failed process was running: /*
1?????????=?????????????????????????????????????????????????????????????????????????????????????????????
2????????????=???????????????/????????????*100%???
3???????????????????????????????????????????????????---????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
4??????????????????[0-24]????????????????????????????????????
5???????????????????????????????????????????????????????????????
6??????????????????????????????????????????????????????????????????
7????????????????????????????????????????????????????????????????????????????????????
8???????????????????????????????????????????????????????????????????????????/????????????????????????*100%;
9???V??????????????????V??????????????????????????????????????????

10??????????????????????????????????????????????????????????????????????????????????????????????????????

""title"" (
""??????"" character varying,
""?????????"" character varying,
"
2016-04-13 11:57:54.702 CST 18502 570b7c87.4846 1103 2016-04-11 18:29:27 CST 0 LOG 0 terminating any other active server processes
2016-04-13 11:57:54.702 CST postgres truckno1_20151116 12490 10.169.9.115:54231 570dc318.30ca 3 idle 2016-04-13 11:55:04 CST 11/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command.
2016-04-13 11:57:54.702 CST readonly truckno1_20151116 8767 10.51.24.164:46535 570d9c59.223f 3 idle 2016-04-13 09:09:45 CST 12/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command.
2016-04-13 11:57:54.702 CST postgres postgres 18580 10.168.105.140:53498 570b7d45.4894 3 idle 2016-04-11 18:32:37 CST 3/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command. pgAdmin III - ?????????
2016-04-13 11:57:54.702 CST readonly truckno1_20151116 18974 10.51.24.164:52460 570b8234.4a1e 3 idle 2016-04-11 18:53:40 CST 2/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command.
2016-04-13 11:57:54.702 CST 18514 570b7c87.4852 2 2016-04-11 18:29:27 CST 1/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command.
2016-04-13 11:57:54.702 CST readonly truckno1_20151116 18975 10.51.24.164:52462 570b8234.4a1f 3 idle 2016-04-11 18:53:40 CST 6/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command.
2016-04-13 11:57:54.702 CST postgres truckno1_20151116 11816 10.168.105.140:56272 570dbaa8.2e28 3 idle 2016-04-13 11:19:04 CST 4/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command. pgAdmin III - ?????????
2016-04-13 11:57:54.703 CST readonly truckno1_20151116 8789 10.51.24.164:46572 570d9c6e.2255 3 idle 2016-04-13 09:10:06 CST 15/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command.
2016-04-13 11:57:54.703 CST readonly truckno1_20151116 7370 10.51.24.164:34108 570c4f4b.1cca 3 idle 2016-04-12 09:28:43 CST 7/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command.
2016-04-13 11:57:54.704 CST postgres truckno1_20151116 14081 10.168.105.140:62479 570c92e3.3701 6 idle 2016-04-12 14:17:07 CST 8/0 0 WARNING 57P02 terminating connection because of crash of another server process The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. In a moment you should be able to reconnect to the database and repeat your command. pgAdmin III - ????????????
2016-04-13 11:57:55.058 CST 18502 570b7c87.4846 1104 2016-04-11 18:29:27 CST 0 LOG 0 all server processes terminated; reinitializing
2016-04-13 11:57:56.787 CST 12528 570dc3c4.30f0 1 2016-04-13 11:57:56 CST 0 LOG 0 database system was interrupted; last known up at 2016-04-13 10:58:49 CST
2016-04-13 11:58:01.596 CST 12528 570dc3c4.30f0 2 2016-04-13 11:57:56 CST 0 LOG 0 database system was not properly shut down; automatic recovery in progress
2016-04-13 11:58:01.607 CST 12528 570dc3c4.30f0 3 2016-04-13 11:57:56 CST 0 LOG 0 redo starts at 3EA/D6B31E20
2016-04-13 11:58:25.203 CST 18502 570b7c87.4846 1105 2016-04-11 18:29:27 CST 0 LOG 0 "setsockopt(TCP_KEEPIDLE) failed: 鏃犳晥鐨勫弬鏁?,,,,,,,,,""
2016-04-13 11:58:25.204 CST,,,12545,"",570dc3e1.3101,1,"",2016-04-13 11:58:25 CST,,0,LOG,00000,connection received: host=10.168.105.140 port=56646"""
2016-04-13 11:58:25.214 CST postgres truckno1_20151116 12545 10.168.105.140:56646 570dc3e1.3101 2 2016-04-13 11:58:25 CST 0 FATAL 57P03 the database system is in recovery mode
2016-04-13 11:58:28.625 CST 18502 570b7c87.4846 1106 2016-04-11 18:29:27 CST 0 LOG 0 "setsockopt(TCP_KEEPIDLE) failed: 鏃犳晥鐨勫弬鏁?,,,,,,,,,""
2016-04-13 11:58:28.625 CST,,,12546,"",570dc3e4.3102,1,"",2016-04-13 11:58:28 CST,,0,LOG,00000,connection received: host=10.168.105.140 port=56647"""
2016-04-13 11:58:28.625 CST postgres truckno1_20151116 12546 10.168.105.140:56647 570dc3e4.3102 2 2016-04-13 11:58:28 CST 0 FATAL 57P03 the database system is in recovery mode
2016-04-13 11:58:57.218 CST 18502 570b7c87.4846 1107 2016-04-11 18:29:27 CST 0 LOG 0 "setsockopt(TCP_KEEPIDLE) failed: 鏃犳晥鐨勫弬鏁?,,,,,,,,,""
2016-04-13 11:58:57.219 CST,,,12547,"",570dc401.3103,1,"",2016-04-13 11:58:57 CST,,0,LOG,00000,connection received: host=10.168.105.140 port=56656"""
2016-04-13 11:58:57.221 CST postgres postgres 12547 10.168.105.140:56656 570dc401.3103 2 2016-04-13 11:58:57 CST 0 FATAL 57P03 the database system is in recovery mode
2016-04-13 11:58:57.225 CST 18502 570b7c87.4846 1108 2016-04-11 18:29:27 CST 0 LOG 0 "setsockopt(TCP_KEEPIDLE) failed: 鏃犳晥鐨勫弬鏁?,,,,,,,,,""
2016-04-13 11:58:57.226 CST,,,12548,"",570dc401.3104,1,"",2016-04-13 11:58:57 CST,,0,LOG,00000,connection received: host=10.168.105.140 port=56657"""

取消 提交回答
全部回答(1)
  • 德哥
    2019-07-17 18:42:14

    记录有多大? 看看是不是被OOM了?

    0 0
相关问答

0

回答

2.3 支持polardb pgsql不

2022-11-03 21:51:09 107浏览量 回答数 0

1

回答

请问各位大佬,cdc连接mongo报错是啥问题呀?

2022-07-22 13:38:28 89浏览量 回答数 1

0

回答

大佬们 mongo cdc 怎么获取mongo的schma

2022-07-13 13:11:53 106浏览量 回答数 0

1

回答

【RDS】RDS PostgreSQL如何通过postgres_fdw和dblink插件实现跨库查询

2022-01-14 15:42:44 468浏览量 回答数 1

1

回答

RDS PostgreSQL如何通过postgres_fdw和dblink插件实现跨库查询?

2022-01-07 21:06:34 1028浏览量 回答数 1

0

回答

求助,在pg 11 的 procedure中 如果 使用 mysql_fdw外部表导致崩溃。

2019-04-25 17:09:33 1593浏览量 回答数 0

0

回答

使用 psql 命令迁移 PostgreSQL 数据

2017-10-18 14:06:54 1460浏览量 回答数 0

2

回答

Why so many getmore operations in mongodb when use mongo_fdw?

2016-09-22 10:21:48 3482浏览量 回答数 2

2

回答

求大神讲解一个关于postgres_fdw外部表的报错。

2016-09-12 13:48:07 3483浏览量 回答数 2

1

回答

pg使用mongo_fdw外部表时,如果外部mongo重启,则pg无法自动重连mongo,pg也必须重启。

2016-06-28 09:30:41 3332浏览量 回答数 1
文章
问答
问答排行榜
最热
最新
相关电子书
更多
PostgresChina2018_余鹏_gogudb—基于FDW实现的PG分库分表插件
立即下载
ApsaraDB for MongoDB
立即下载
HTAP DB HTAP DB —System : ApsaraDB HBase Phoenix and Spark
立即下载