PostgreSQL Protocol: Server-Side Prepared Statements

Learn to write the server-side prepared statements using PostgreSQL and the application code.

We'll cover the following

Extended query
Example
Try it yourself

It’s possible to send the query string and its arguments separately on the wire by using server-side prepared statements. This is a pretty common way to do it, mostly because PQexecParams isn’t well-known, though it made its debut in PostgreSQL 7.4 in 2003. To this day, a lot of PostgreSQL drivers still don’t expose the PQexecParams facility, which is unfortunate.

Server-side prepared statements can be used in SQL thanks to the prepare and execute commands syntax, as in the following example:

Get hands-on with 1400+ tech skills courses.

Part I: Preface

Introduction to PostgreSQL

Part II: Introduction to Structured Query Language

Part III: Writing SQL Queries

Business Logic

A Small Application

The SQL REPL: An Interactive Setup

Indexing in PostgreSQL

Part IV: SQL Toolbox

SQL Tools

Managing Output in SQL

Understanding Nulls

Window Functions

Relations and Joins

Part V: Data Types

Serialization and Deserialization

PostgreSQL Data Types 101

Denormalized Data Types

Part VI: Data Modeling

Object Relational Mapping and Tooling for Database Modeling

Normalization

Practical Use Case: Geonames

Modelization Anti-Patterns

Denormalization

Not Only SQL

Part VII: Data Manipulation and Concurrency Control

Another Small Application

Isolation and Locking

Computing and Caching in SQL

Triggers

Listen and Notify

Batch Update, MoMA Collection

Part VIII: PostgreSQL Extensions

What’s a PostgreSQL Extension?

Auditing Changes with hstore

Million Song Dataset

Using Trigrams for Typos

Denormalizing Tags with intarray

The Most Popular Pub Names

Geolocation with PostgreSQL

Counting Distinct Users with HyperLogLog

Appendix

PostgreSQL Protocol: Server-Side Prepared Statements