ahsanhadi
commented
7 years ago Are you building from the latest code from github? I was able to run these commands successfully..
On Wed, Jan 11, 2017 at 7:32 PM, RocketEnvy notifications@github.com wrote:
Following the Readme.md everything seems to go okay until I actually try to do a select. There is nothing about it in the Mongo logs. Postgres log is:
==> postgresql/postgresql-9.5-main.log <== 2017-01-11 07:23:59 MST [14910-1] g@g ERROR: relation "notes" does not exist at character 15 2017-01-11 07:23:59 MST [14910-2] g@g STATEMENT: select from notes; 2017-01-11 07:24:43 MST [2839-47] LOG: server process (PID 14915) was terminated by signal 11: Segmentation fault 2017-01-11 07:24:43 MST [2839-48] DETAIL: Failed process was running: select from notes; 2017-01-11 07:24:43 MST [2839-49] LOG: terminating any other active server processes 2017-01-11 07:24:43 MST [14759-2] WARNING: terminating connection because of crash of another server process 2017-01-11 07:24:43 MST [14759-3] DETAIL: 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. 2017-01-11 07:24:43 MST [14759-4] HINT: In a moment you should be able to reconnect to the database and repeat your command. 2017-01-11 07:24:43 MST [14917-1] g@gtest FATAL: the database system is in recovery mode 2017-01-11 07:24:43 MST [2839-50] LOG: all server processes terminated; reinitializing 2017-01-11 07:24:43 MST [14918-1] LOG: database system was interrupted; last known up at 2017-01-11 07:12:15 MST 2017-01-11 07:24:43 MST [14918-2] LOG: database system was not properly shut down; automatic recovery in progress 2017-01-11 07:24:43 MST [14918-3] LOG: invalid record length at 0/1AE05F8 2017-01-11 07:24:43 MST [14918-4] LOG: redo is not required 2017-01-11 07:24:43 MST [14918-5] LOG: MultiXact member wraparound protections are now enabled 2017-01-11 07:24:43 MST [2839-51] LOG: database system is ready to accept connections 2017-01-11 07:24:43 MST [14922-1] LOG: autovacuum launcher started
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/EnterpriseDB/mongo_fdw/issues/71, or mute the thread https://github.com/notifications/unsubscribe-auth/AHmqpAnSaAtTSln1AMwy1iVwbdGORKQ7ks5rROgHgaJpZM4LgpNd .
-- Ahsan Hadi Snr Director Product Development EnterpriseDB Corporation The Enterprise Postgres Company
Phone: +92-51-8358874 Mobile: +92-333-5162114
Website: www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb
This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
RocketEnvy
Following the Readme.md everything seems to go okay until I actually try to do a select. There is nothing about it in the Mongo logs. Postgres log is: