After quite a pause we continue the #fdw foreign data wrappers series of posts. In this post we will deal with MariaDB database access from within Postgres.
Main idea of this post is to demonstrate postgres major version upgrade process for the case when postgres runs within docker container.
Demonstrated approach uses pg_dumpall utility. In any case it does not pretend to be the "best" approach.
There are other options availabe such as pg_upgrade or setting up a replication server.
Moreover, for big databases pg_dumpall might be non optimal or even not feasible solution.
But as said at the beginning, idea is to demonstrate possible upgrade process for containerized postgres installation.
As many other databases Postgres supports access management framework via privileges which are provided to the users.
In terms of SQL it means a pair of commands GRANT and REVOKE.
To simplify things to the users postgres also supports massALL option for these commands.
Specifying either GRANT ALL or REVOKE ALL allows to apply command against multiple objects or against multiple privileges or for a mix of both.
Postgres foreign data wrapper for MongoDB database
This is part 4 of #fdw foreign data wrappers series of posts.
Earlier we have introduced wrappers for mysql, oracle and sqlite databases.
In this post we will connect to MongoDB database from within Postgres.
This is part 3 of #fdw foreign data wrappers series of posts.
Initial part 1 was about connectivity to MySQL database.
Next part 2 was related to accessing Oracle database.
In this post we will access SQLite database from within Postgres.
As a contractor of Epam company I'm currently working on Oracle 2 Postgres project migration into AWS cloud.
Being on tech team lead position I've been asked to present our work on official Epam's webinar as a speaker.
I'm thankful to the Epam for the given opportunity to share our experience with a wide auditory.
This is part 2 of #fdw foreign data wrappers series of posts.
In part 1 it was described what foreign data mean in Postgres as well as provided an example of connection to MySQL database.
In this post we will deal with accessing data in Oracle database.
This is the first part of #fdw foreign data wrappers series of posts.
One of the great features in Postgres is the ability to access data stored in outer sources as if they were stored in ordinary tables within the database.
There is no requirement to the source as is. For example, it can be another RDBMS such as Oracle or MySQL.
But we are not limited to relational databases only. It can be also just a csv file or even Hadoop file system objects.
All you need to do to get access to these data is to install corresponding foreing data wrapper extension.
Postgres allows automatic types conversion to some extent.
It supports fully automated implicit conversion, more constrained implicit conversion on assignment operation only and explicit conversion specified via CAST function or :: operator.