Simulating UPDATE or DELETE with LIMIT in Postgres: CTEs to The Rescue!

Crunchy Bridge delivers a fully managed cloud Postgres service available on multiple clouds so you can focus on your application, not your database.

Get started with Crunchy Bridge by creating your account and provision your production ready database on the cloud of your choice.

A fully managed cloud Postgres service that allows you to focus on your application, not your database.

Kubernetes-Native, containerized PostgreSQL-as-a-Service for your choice of public, private, or hybrid cloud.

Integrated high-availability PostgreSQL solution for enterprises with "always on" data requirements.

There have certainly been times when using PostgreSQL, that I’ve yearned for an  UPDATE  or  DELETE  statement with a  LIMIT  feature. While the SQL standard itself has no say in the matter as of SQL:2016, there are definite cases of existing SQL database dialects that support this.

Before we dig into the nitty-gritty, let's look at some use cases for such a feature. The primary desire for this behavior is to break large transactions up into smaller ones, for multiple reasons:

Leave a Comment