Last Wednesday, March 26, we hosted the second of five virtual Extension Mini-Summits in the lead up to the big one at the Postgres Development Conference (PGConf.dev) on May 13 in Montreal, Canada. Peter Eisentraut gave a very nice presentation on the history, design decisions, and problems solved by “Implementing an Extension Search Path”. That talk, plus another 10-15m of discussion, is now available for your viewing pleasure:
If you’d like to attend any of the next three Mini-Summits, join the Meetup!
Once again, with many thanks again to Floor Drees for the effort, here’s the transcript from the session.
Introduction
Floor Drees introduced the organizers:
- David Wheeler, Principal Architect at Tembo, maintainer of PGXN
- Yurii Rashkovskii, Omnigres
- Keith Fiske, Crunchy Data
- Floor Drees, Principal Program Manager at EDB, PostgreSQL CoCC member, PGDay Lowlands organizer
Peter Eisentraut, contributor to PostgreSQL development since 1999, talked about implementing an extension search path.
The stream and the closed captions available for the recording are supported by PGConf.dev and their gold level sponsors, Google, AWS, Huawei, Microsoft, and EDB.
Implementing an extension search path
Peter: Thank you for having me!
I’m gonna talk about a current project by me and a couple of people I have worked with, and that will hopefully ship with Postgres 18 in a few months.
So, what do I know about extensions? I’m a Postgres core developer, but I’ve developed a few extensions in my time, here’s a list of extensions that I’ve built over the years.