PostgreSQL 15 will include some more regexp functions
While migrating from other databases like Oracle to PostgreSQL, we may come across some functionalities that may be only available with a complex work-around. At MigOps, we have migrated many customers from Oracle to PostgreSQL and I have personally seen many scenarios where direct equivalent is not possible. One of them was while working with regular expressions. There
MigOps announcing the support for Babelfish on any Cloud Platform
AWS has recently announced the release of Babelfish extension that supports SQL Server TDS protocol. In order to have this extension work with PostgreSQL, it required some changes to PostgreSQL. However, the original thought of having the required hooks integrated into PostgreSQL has not been considered by the PostgreSQL Community (see the discussion here). For this reason, AWS
Migration Management and schema version control in PostgreSQL
Version control of any code is essential for every organization. All organizations use their own preferred tools like git, svn, perforce etc. As I was working on a new requirement, which is about porting the current CI/CD pipeline to PostgreSQL, I needed to look for a tool which will take care of the schema changes. In this use
Organizing PostgreSQL codebase using templates in Golang
While migrating to PostgreSQL, have you ever wondered whether you could make changes to SQL-only code without triggering a build, re-deployment, or even a restart? Have you ever attempted packaging software as a binary and allowing clients to execute their own compatible queries on any DB engine at no additional cost? In such cases, a better approach to
Stored Procedure OUT Parameters in PostgreSQL 14
PostgreSQL global development group generally announces a new release every year, with several new features. With an increase in the number of contributions and contributors, the new version PostgreSQL 14 released on September 30th, 2021, with several important features. As a developer and a database migration expert, I am happy to say that there are several developer friendly
SELECT FOR UPDATE and its behavior with foreign keys in PostgreSQL
The general approach followed by developers is to pre-acquire the lock(FOR UPDATE)on the data sets that are being updated/deleted concurrently. This approach may be considered to solve the dead lock problem or to control the concurrent access to one or more rows, but could sometimes lead to an unnecessary locking behavior. In this article we shall discuss about