How to install external extensions in GCP's PostgreSQL - postgresql

I see here that only allowed extensions can be installed on PostgreSQL in Google Cloud Platform. Is there any possibility to add an extension that is not listed in supported extensions? The extension I need is pg_semver.

There are two options here for your use case:
Use a Compute Engine instance as SQL database, rather than
CloudSQL and you will be able to install any extension you would
need to.
As stated on the official documentation you can open a Feature Request (FR) to the CloudSQL eng
team in order to evaluate it and let you know if it will be
implemented or not in the future.
Bear in mind that feature requests
have not ETA.

Related

Confluence migration from cloud to server

We have migrated a space from cloud instance to server instance,in cloud instance we were using "Plantuml diagrams for confluence" but in server we are using "Confluence PlantUML Plugin" .so macro name are different in both cloud and server ,so macro name for cloud is "plantumlcloud" but for server it is "plantuml".so ,in pages after migration it is showing "plantumlcloud" not a valid macro ,kindly help to resolve.
In general, migration of confluence spaces to another application which is not running the same plugins will cause any functionality of that plugin to break.
If you migrate hosting platforms, and have the equivalent version of the plugin for your new platform, created by the same developer, in most cases you will retain functionality, however there will often be differences between versions.
These differences are found especially when downgrading, and moving from cloud to server is a very definite example of a downgrade, as cloud will always run the latest version.
In general I would reccomend against a migration from cloud to server, and when it must be done, time should be spent to ensure compatability with all plugins, and migration guides and plans should be made and followed.
As commented by #tgdavies, there seems to be an equivelent version of the plugin you were using on cloud, so hopefully that can resolve your issue.

How do I choose a local MySQL version that will be compatible with our future switch to CloudSQL?

For simplicity and cost, we are starting our project using local MySQL running on our GCE instances. We will want to switch to CloudSQL some months down the road.
Any advice on avoiding MySQL version conflicts/challenges would be much appreciated!
The majority of the documentation is for MySQL 5.7 so as an advice I recommend you use this version and review migrating to cloudsql concept this is a guide that will guide you through how to migrate safely which migration methods exist and how to prepare you MySQL database.
Another advice which I can give you is make the tutorial migrating mysql to cloud using automated workflow tutorial this guide also says that the any MySQL database running version 5.6 or 5.7 allows you to take advantage of the Cloud SQL automated migration workflow this tutorial is important to know how works and how deploy a source MySQL database on Compute Engine. The sql page will give you more tutorials if you want to learn more.
Finally I suggest to you check de sql pricing to be aware about the billing and also I suggest to you create a workspace with this you can have more transparency and more control over your billing charges by identifying and tuning up the services that are producing more log entries.
I hope all the information that I'm giving you are helpful.

Is it possible to support orafce in google postgres cloud sql

we used orafce for our oracle to postgres migration, it work very well.
https://github.com/orafce.
Recently we try to migrate to cloud db, we choose the google cloud, however, I found that the google cloud is not support the orafce extension.
https://cloud.google.com/sql/docs/postgres/extensions#postgresql-extensions-supported-by-cloud-sql
Is it possible to support orafce extension in google cloud?
At the moment “orafce” extension is not supported.
As you can see on this public issue tracker, many other users of Cloud SQL wish for this, I would recommend you to “star” or +1 this public issue in order to show your interest for this feature and by +1 it you will be updated for any changes on the implementation of this feature.

Postgresql :unable to Install HTTP extension on Amazon RDS

I am trying to get response from API into Postsgresql.
For this I have installed respective HTTP extension
from
http://www.postgresonline.com/journal/archives/371-http-extension-for-windows-64-and-32-bit.html
In my local system .
Current issue is that my database server is on amazon aws. So now I want to replicate same files/modules on server.
But I'm not much aware about it.
While I have tried
create extension http
then after I tried to get to know the supported extension by using this
show rds.extensions
Then I didn't found the HTTP extension there.
SO please let me know how can I place downloaded HTTP extension file on amazon rds??
If the extension is not among the supported ones from ...
SHOW rds.extensions;
... then you are out of luck, for all I know.
In particular, the "http extension" requires to install binaries in the file system of a Windows server.
The RDS Postgres installations I know run on Red Hat Linux, not Windows. And Amazon does not allow direct access to the underlying file system - which can be a pain. We tried to install additional unaccent dictionaries, but no dice.
You could talk to their support, maybe you have more luck.

Does cockroachdb support extensions?

I am wondering whether cockroachdb supports extensions such as time-scale and others?, because I have a project which requires a third party postgres extension in conjunction with cockroachdb.
No, CockroachDB does not support any PostgreSQL extensions. It may one day support features from some of the most popular extensions, but it is very unlikely that it will ever be possible to use arbitrary PostgreSQL extensions directly.
If you are looking for a scale-out SQL database that supports both PostgreSQL client API and its extensions, I would encourage you to take a look at YugaByte DB. We are reusing the PostgreSQL codebase on top of our sharded replicated transactional layer, rather than building a SQL engine from scratch, and that will allow us to stay compatible with new PostgreSQL features as well as extensions.