# Introducing Extensions

DevFeed: [Introducing Extensions](<https://devfeed.tech/articles/introducing-extensions-34398.md>)

Original publisher: [Read original article](<https://tapoueh.org/blog/2010/10/introducing-extensions/>)

Author: Dimitri Fontaine PostgreSQL Major Contributor; Author

Published: 2010-10-21T11:45:00Z

Content type: article

Language: en

Sources: [Dimitri Fontaine](<https://devfeed.tech/sources/dimitri-fontaine.md>)

Topics: [Extension](<https://devfeed.tech/topics/extension.md>), [like](<https://devfeed.tech/topics/like.md>), [backups](<https://devfeed.tech/topics/backups.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [backups](<https://devfeed.tech/tags/backups.md>), [code](<https://devfeed.tech/tags/code.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>)

## AI overview

An introduction to PostgreSQL extensions, describing how they can add custom code, behavior, data types, operators, functions, and index support. The article explains extensions as separately managed scripts, with metadata and dependencies that allow extension-related objects to be excluded from database dumps and reinstalled from the filesystem.

## Source excerpt

After reading Simon's blog post, I can't help but try to give some details about what it is exactly that I'm working on. As he said, there are several aspects to extensions in PostgreSQL, it all begins here: Chapter 35. Extending SQL. It's possible, and mostly simple enough, to add your own code or behavior to PostgreSQL, so that it will use your code and your semantics while solving user queries. That's highly useful and it's easy to understand how so when you look at some projects like PostGIS, ip4r (index searches of ip in a range, not limited to CIDR notation), or our own Key Value Store, hstore.