Skip to content

Latest commit

 

History

History
231 lines (163 loc) · 7.37 KB

doc-template.md

File metadata and controls

231 lines (163 loc) · 7.37 KB
Raw
layout title nav_order
default
Compiling Babelfish from source
2

Compiling Babelfish from source

If you want to compile Babelfish on your own, you need to follow a couple of steps to produce a working binary. In this section, we will describe how this works on Linux (and thus UNIX-style systems in general).

Getting the source code

The first thing to do is to actually download the source code you want to build. Babelfish is separated into two repositories, the first of them contains the PostgreSQL database engine, with some changes that enables the protocols, language parsers, and more features to be hooked into PostgreSQL that are required by Babelfish to work. The second one contains extensions to support the T-SQL protocol, the T-SQL language, the TDS Protocol, etc.

The Babelfish for PostgreSQL engine source code can be downloaded from here.

The Babelfish extensions source code can be downloaded from here.

If you have git installed, you can clone the repos with the following command:

git clone https://github.com/babelfish-for-postgresql/postgresql_modified_for_babelfish.git
git clone https://github.com/babelfish-for-postgresql/babelfish_extensions.git

Preparing your system

To compile Babelfish, you have to make sure that a variety of software components are available on your system. These packages should be part of every modern Linux distribution, under similar - but not identical - names.

Also keep in mind that you will need a user with root privileges, so that you are able to run commands with sudo

If you want to run more than just the bare version of Babelfish, we recommend installing the following additional packages on top of the hard requirements listed above.

If you happen to use Debian or Ubuntu, you might want to use the following commands to install dependencies:

{{ core-prerequisites }}

Compiling the code

Before compiling the Babelfish for PostgreSQL source code, we need to configure the build. To do that we need to run the configure script in the directory where you have downloaded the Babelfish for PostgreSQL engine sources:

{{ default-configure }}

The above would configure the installation path under /usr/local/pgsql; if you want to change the installation directory, you can use the prefix flag. Therefore, if you want to change the path to /usr/local/pgsql-13.4, you can run the configure script as follows.

{{ preffix-configure }}

Building Babelfish for PostgreSQL engine

Now that we have configured the source tree, is important to configure the installation folder.

INSTALLATION_PATH=<the path you specified as prefix>
{{ installation-path }}

To avoid installation errors, you should own the installation directory. You can can change the ownership of the installation path with the following command:

sudo chown -R <your user>:<your group> "$INSTALLATION_PATH"

For example, if your installation path is /usr/local/pgsql-13.4 and your user is johndoe, the command should be as follows:

{{ own-installation }}

Now we can build Babelfish with the following commands:

{{ compile-core }}

Building Babelfish Extensions

In order to build the extensions we would need to install some additional tools:

Additional requied tools

You can install most of these tools by running the command:

{{ extension-prerequisites }}
Installing Antlr4 runtime

For Antlr4 4.9.2 Runtime, there are no available binaries for C++ in Ubuntu Focal, so it's necessary to compile it from source. Versions below 4.9 have not been fully tested yet.

To install the Antlr4 runtime, we need to have the Antlr4 .jar. Babelfish extensions source code includes this .jar in the path /contrib/babelfishpg_tsql/antlr/thirdparty/antlr.

Keeping this in mind, we can install Antlr4 runtime by running:

{{ antlr-download }}

EXTENSIONS_SOURCE_CODE_PATH="<the patch in which you downloaded the Babelfish extensions source code>"

{{ compile-antlr }}

Now that we have the antlr4 runtime installed, we need to copy the libantlr4-runtime.so.4.9.2 library into the installed Babelfish for PostgreSQL engine libs folder. We can do that by running the following command:

{{ copy-antlr-runtime }}

Build and install the extensions

Now that we have all of the tools installed to build the Babelfish extension, we need to configure some environment variables:

  • PG_CONFIG: should point to the location of the pg_config file in the Babelfish for PostgreSQL engine installation, in our case: $INSTALLATION_PATH/bin/pg_config.

  • PG_SRC: should point to the location of the Babelfish for PostgreSQL engine source folder.

  • cmake: should contain the path of the cmake binary

Supposing that you have installed the Babelfish for PostgreSQL engine in /usr/local/pgsql-13.4/, you have downloaded the Babelfish for PostgreSQL engine source code in ~/postgresql_modified_for_babelfish, and cmake is installed in /usr/local/bin/cmake, the environment variables set up would be like this:

export PG_CONFIG=/usr/local/pgsql-13.4/bin/pg_config
export PG_SRC=$HOME/postgresql_modified_for_babelfish
export cmake=/usr/local/bin/cmake

Now we are all set to build the extensions. To do so, we need to go to the contrib folder in the Babelfish extension source code, and then build the extensions one by one. We do it with the following script:

{{ compile-extensions }}

Once all extensions have been compiled you can start PostgreSQL manually.

Further installations steps

Before starting Babelfish we need to do some changes in the installation folder. This is because, PostgreSQL wont start if its owner has root access. Also, we need to create a directory for PostgreSQL to store its data.

Let's first, create the data directory, in this example we will use /usr/local/pgsql/data as the data folder.

{{ data-path }}

Now, let's create a postgres user

{{ add-postgres-user }}

With the created user, we can change the ownership the of the Babelfish binaries, and the data directory.

{{ own-postgres-installation }}

Now we can use the created postgres user to initialize the database directory.

{{ init-database }}

Once the data directory has been initialized, we need to change the postgresql.conf file, by uncommenting and setting the following properties:

listen_addresses = '*'
shared_preload_libraries = 'babelfishpg_tds'

Now you can start Babelfish by running the command:

{{ start-database }}