I am using Pivotal Greenplum sandbox.
Want to stop entry into log_alert_* tables? Which are under gpperfmon database.
Is, there is a way to stop it?
Any help will be appreciated.
you can disable gpperfmon
gpconfig -c gp_enable_gpperfmon -v off
gpstop -arf
Related
just starting testcontainers. I love the idea. thanks for investing in this project.
I am trying to create a simple postgres 14.5 container (and susceeded) and now I am trying to populate it using the .withInitScript() method.
the file I am feeding into the init method is a dump I created with pg_dumpall.
testcontainers fails for many parsing/validation reasons. each time I delete a portion and another reason pops up.
should I be able to succesfully use the withInitScript with pg_dump files?
BTW, using pg_dump for my main DB also has many similar issues.
thanks!
Try copying the script to the container so postgres will execute. Although this comment BTW, using pg_dump for my main DB also has many similar issues. makes me wonder if it will work because it also fails when you are using the database directly if I understood correctly.
new PostgreSQLContainer("postgres:14.5")
.withCopyFileToContainer(
MountableFile.forClasspathResource("init.sql"),
"/docker-entrypoint-initdb.d/init.sql"
);
We recommend to use liquibase or flyway to manage database changes.
hi and thanks for the help
I have managed to make things work by stripping some things from the sql dump and using the copyFileToContainer
thanks
I upgraded my dev server with mysql 8.0.24 but it doesn't work for me. I keep getting a fatal crash every time a query uses GROUP_CONCAT(DISTINCT... and there are no rows because of the WHERE. Anyway, I'd like to rollback to 8.0.23. Was the file format upgraded? Can I safely go back to 8.0.23?
Thank you.
After some reading, it's not easy to downgrade mysql. Mysql itself says it's not possible: https://dev.mysql.com/doc/refman/8.0/en/downgrading.html
I found some possible solution: https://subscription.packtpub.com/book/big_data_and_business_intelligence/9781788395809/1/ch01lvl1sec18/downgrading-from-mysql-8-0
But in the end, I decided to revert the whole dev server to the last backup; that was easier, just a few clicks and back on my feet.
I have janusgraph database, in which all indexes were built.But the status of some of those indexes is installed. Now I am trying to update those Indexes to the registered and then to enabled. So I have done some research and I found this Action(schemaAction).But I don't know the syntax and also how to use graph.openManagement().updateIndex().
Any suggestions regarding this issue or if there is anything other than this procedure, then please let me know it.
Thanks in advance!
If there are any open transactions while creating the indexes they might get stuck in the INSTALLED state.
You can find a clear explanation here.
After rolling back your open transactions and closing open instances, try reindexing.
Note: Block until the SchemaStatus transitions from INSTALLED to REGISTERED, after running the reindex command. Try to run groovy script instead of running the commands directly on gremlin console for building the indexes. Please find the sample script below.
import org.janusgraph.graphdb.database.management.ManagementSystem
mgmt = graph.openManagement();
mgmt.updateIndex(mgmt.getGraphIndex("giftIdByGift"), SchemaAction.REGISTER_INDEX).get();
ManagementSystem.awaitGraphIndexStatus(graph, "giftIdByGift").call();
mgmt.commit();
mgmt = graph.openManagement();
mgmt.updateIndex(mgmt.getGraphIndex("giftIdByGift"), SchemaAction.REINDEX).get();
ManagementSystem.awaitGraphIndexStatus(graph, "giftIdByGift").status(SchemaStatus.ENABLED).call();
mgmt.commit();
Does anyone know how to recreate import/export from parse.com on parse server?
Or even point me in the right direction to do this?
You can use a third party MongoDB tool for that like MongoChef.
Or you can use a Mongo query like mongodump:
mongodump -d <database_name> -o <directory_backup>
And to "restore/import" that, i used (from directory_backup/dump/):
mongorestore -d <database_name> <directory_backup>
Check out this stackoverflow answer for more one that.
Deb. Squeeze, Postgres 8.4, Slony 1.2.21
I've created a master > slave cluster which has done the initial copy. However, I can't get any more data to replicate. I've always been a bit baffled by what commands should be run to start the required processes/daemons at each end.
Can anyone enlighten me?
Cheers.
OK, got the little bugger sorted. Potential Slony users note that (currently) Slony doesn't replicate Truncate statements, use delete from instead.
This meant my original data was still in the slave and the PK clashed with the new data ,so it wasn't updated.