Four Compelling Use Cases for PostgreSQL Table Functions
Take a look at four realistic use cases that call for PostgreSQL user-defined table functions and see how each is met using complete, self-contained code examples.
Take a look at four realistic use cases that call for PostgreSQL user-defined table functions and see how each is met using complete, self-contained code examples.
Learn how to implement user-defined table functions, in all variants, using generalized use cases.
Read through an introduction to PostgreSQL’s table functions and their use in distributed SQL databases. The blog series will cover the basics of table functions, the use of built-in SQL table functions, and the implementation of user-defined table functions.
These days, most monolithic SQL databases support stored procedures. This support first emerged in commercially available offerings in the late nineteen eighties. However, stored procedure support is not yet standard in distributed SQL databases. In fact, YugabyteDB is just one of two in this category—supporting stored procedures written in PostgreSQL’s PL/pgSQL. (Aurora also supports stored procedures.) This post recaps the case for stored procedures that motivated their introduction all those years ago. And it describes a performance experiment that measures one of the benefits brought by using stored procedures: the reduction in client-server round trips for multi-statement business transactions.
…
If a partial index is used, instead of a regular one, on a nullable column—where only a small fraction of the rows have not null values for this column—then the response time for inserts, updates, and deletes can be shortened significantly. As a bonus, the response times for single row selects shorten a little bit too. This post explains what a partial index is, shows how to create one, describes the canonical use case that calls for a partial index,
…
Note added on October 31, 2019
A lot has happened since this post was published in July 2019. Back then, the current YugabyteDB version was 1.2.10. And now, it’s 2.0.3. My original text included some caveats and comments like “Until this support is added in a future release…”. Now, no caveats are needed. I therefore revised my text and the companion downloadable code to remove all reference to those earlier, interim,
…
I’m thrilled at the prospect of what lies ahead of me in my new job at YugaByte. I’ve just started in the role of Developer Advocate for YugabyteDB. This is an open source, cloud native, distributed SQL database—in other words, a database for the modern world. There’s an excellent brief description here.
I made this move a couple of weeks ago after almost thirty years at Oracle. I started with Oracle in the UK,
…