How-to: The PGExercises PostgreSQL Tutorial Running on a Distributed SQL Database
PgExercises is a sample dataset used to power the PostgreSQL Exercises website. The site is comprised of over 80 exercises designed to be used as a companion to the official PostgreSQL documentation. The exercises on the PGExercises site range from simple SELECT statements and WHERE clauses, through JOINs and CASE statements, then on to aggregations, window functions, and recursive queries.
The dataset consists of 3 tables (members, bookings, and facilities) and table relationships as shown in the ER diagram below:
In this post we are going to walk you through how to download and install PGExercises on the YugaByte DB distributed SQL database with a replication factor of 3.
Download and Install YugaByte DB
For complete instructions on how to get up and running on a variety of platforms including prerequisites, check out our Quickstart Guide. In the following section we’ll cover the basic steps for getting up and running in just a few minutes with a local 3 node cluster on your Mac.
Download and Extract YugaByte DB
$ wget https://downloads.yugabyte.com/yugabyte-188.8.131.52-darwin.tar.gz
$ tar xvfz yugabyte-184.108.40.206-darwin.tar.gz && cd yugabyte-220.127.116.11/
Note: The above instructions are for version 1.3.0. To find the latest version of YugaByte DB, visit the quickstart page.
Configure Loopback Addresses
Add a few loopback IP addresses for the various YugaByte DB nodes to use.
sudo ifconfig lo0 alias 127.0.0.2
sudo ifconfig lo0 alias 127.0.0.3
sudo ifconfig lo0 alias 127.0.0.4
sudo ifconfig lo0 alias 127.0.0.5
sudo ifconfig lo0 alias 127.0.0.6
sudo ifconfig lo0 alias 127.0.0.7
Create a 3 Node Cluster
With the command below you’ll create a 3 node cluster with a replication factor of 3.
$ ./bin/yb-ctl --rf 3 create
Check the Status of the YugaByte DB Cluster
Now let’s take a look at the status of the cluster and all the nodes that comprise it.
$ ./bin/yb-ctl status
As you can see from the output, we have three nodes running locally with a replication factor of 3. This means that every piece of data is being replicated on all three nodes.
Enter the YSQL shell
Next run the
ysqlsh command to enter the PostgreSQL shell.
$ ./bin/ysqlsh --echo-queries
Type "help" for help.
We are now ready to build the PGExercises database.
Download and Install the PGExercises Database
Download the PGExercises Scripts
You can download the PGExercises database that is compatible with YugaByte DB from our GitHub repo. The two files are:
- clubdata_ddl.sql which creates tables and other database objects
- clubdata_data.sql which loads the sample data into the exercises database
Create the Exercises Database
CREATE DATABASE exercises;
Let’s confirm we have the exercises database by listing out the databases on our cluster.
Switch to the exercises database.
postgres=# \c exercises
You are now connected to database "exercises" as user "postgres".
Build the Exercises Tables and Objects
exercises=# \i /Users/yugabyte/clubdata_ddl.sql
We can verify that all 3 of our tables have been created by executing:
Load Sample Data into Exercises
Next, let’s load our database with sample data.
exercises=# \i /Users/yugabyte/clubdata_data.sql
Let’s do a simple SELECT to pull data from the bookings table to verify we now have some data to play with.
exercises=# SELECT * FROM bookings LIMIT 5;
Try the PGExercises Tutorial
That’s it! You are ready to start working through the PGExercises tutorial with YugaByte DB as the backend. PGExercises is made up of 81 exercises and broken into the following major sections:
- Simple SQL Queries
- JOINs and Subqueries
- Modifying Data
- Working with Timestamps
- String Operations
- Recursive Queries
Note that all of the exercises on the site will work with YugaByte DB with the exception of the following:
- This JOIN example has a bug and won’t return the correct row numbers. The GitHub issue can be tracked here.
- In this string operation exercise you might notice that our sort order will be different. This is because we hash partition our data. As a result, row ordering is expected to be different.
- In the calculated UPDATE example, you will get an error because “FROM clause in UPDATE” is not yet supported. You can track the issue on GitHub here.
- The exercise which demonstrates a DELETE based on a subquery will return an error. You can track the resolution of this issue on GitHub here.