Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot start the pgrocks after installation #45

Open
Change72 opened this issue Oct 30, 2022 · 4 comments
Open

Cannot start the pgrocks after installation #45

Change72 opened this issue Oct 30, 2022 · 4 comments

Comments

@Change72
Copy link

My OS: Ubuntu 20.04
I followed the readme and finished the installation.
By the way, I notice it does not support a secondary index in the limitation part. Just to make sure, does it still support spatial index(R-Tree)?

● postgresql.service - PostgreSQL RDBMS
Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
Active: active (exited) since Sat 2022-10-29 23:27:32 MST; 8min ago
Process: 2026248 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 2026248 (code=exited, status=0/SUCCESS)

Oct 29 23:27:32 en4217753l systemd[1]: Starting PostgreSQL RDBMS...
Oct 29 23:27:32 en4217753l systemd[1]: Finished PostgreSQL RDBMS.

2022-10-29 19:37:47.000 MST [1788256] LOG: starting PostgreSQL 13.8 (Ubuntu 13.8-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
2022-10-29 19:37:47.000 MST [1788256] LOG: listening on IPv4 address "127.0.0.1", port 5432
2022-10-29 19:37:47.001 MST [1788256] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-10-29 19:37:47.002 MST [1788257] LOG: database system was shut down at 2022-10-29 19:37:45 MST
2022-10-29 19:37:47.005 MST [1788256] LOG: database system is ready to accept connections
2022-10-29 19:57:44.374 MST [1788256] LOG: received fast shutdown request
2022-10-29 19:57:44.374 MST [1788256] LOG: aborting any active transactions
2022-10-29 19:57:44.376 MST [1788256] LOG: background worker "logical replication launcher" (PID 1788263) exited with exit code 1
2022-10-29 19:57:44.376 MST [1788258] LOG: shutting down
2022-10-29 19:57:44.382 MST [1788256] LOG: database system is shut down
2022-10-29 19:57:44.537 MST [1816513] FATAL: could not load library "/usr/lib/postgresql/13/lib/kv_fdw.so": /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block
2022-10-29 19:57:44.538 MST [1816513] LOG: database system is shut down
pg_ctl: could not start server
Examine the log output.
2022-10-29 23:18:36.461 MST [2017198] FATAL: could not load library "/usr/lib/postgresql/13/lib/kv_fdw.so": /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block
2022-10-29 23:18:36.461 MST [2017198] LOG: database system is shut down
pg_ctl: could not start server
Examine the log output.
2022-10-29 23:27:32.545 MST [2026247] FATAL: could not load library "/usr/lib/postgresql/13/lib/kv_fdw.so": /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block
2022-10-29 23:27:32.545 MST [2026247] LOG: database system is shut down
pg_ctl: could not start server
Examine the log output.

@jsc0218
Copy link
Member

jsc0218 commented Oct 30, 2022

This fdw version does not support secondary index. Though we are developing a table_am version, but R-tree is not in our recent road map currently. Could you briefly show your use cases why using rocksdb & r-tree?

@Change72
Copy link
Author

I need to write plenty of spatial data during the experiment. Rocksdb becomes a good choice since its high write performance, and I can also disable the compaction.

As the experiment finished, I want to build a r-tree spatial index to accelerate the query efficiency.

@Change72
Copy link
Author

Change72 commented Nov 2, 2022

Hi, I want to run pgrocks and do some tests. But the upper problem cannot be solved: "could not load library "/usr/lib/postgresql/13/lib/kv_fdw.so": /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block"

@jsc0218
Copy link
Member

jsc0218 commented Nov 4, 2022

Can you try 13.2 version instead? Otherwise, you may have to wait for our update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants