# prefix 1.1.0

DevFeed: [prefix 1.1.0](<https://devfeed.tech/articles/prefix-1-1-0-34355.md>)

Original publisher: [Read original article](<https://tapoueh.org/blog/2009/11/prefix-1.1.0/>)

Author: Dimitri Fontaine PostgreSQL Major Contributor; Author

Published: 2009-11-30T11:10:00Z

Content type: release

Language: en

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

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [bug](<https://devfeed.tech/topics/bug.md>), [ordering](<https://devfeed.tech/topics/ordering.md>), [Code](<https://devfeed.tech/topics/code.md>), [version](<https://devfeed.tech/topics/version.md>), [GitHub Issues](<https://devfeed.tech/topics/github-issues.md>)

Tags: [btree](<https://devfeed.tech/tags/btree.md>), [bug](<https://devfeed.tech/tags/bug.md>), [code](<https://devfeed.tech/tags/code.md>), [function](<https://devfeed.tech/tags/function.md>), [indexes](<https://devfeed.tech/tags/indexes.md>), [ordering](<https://devfeed.tech/tags/ordering.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [version](<https://devfeed.tech/tags/version.md>)

## AI overview

The prefix 1.1.0 release fixes the btree operator class behavior for the prefix range type in PostgreSQL. The change requires rebuilding existing btree indexes, prompting a version number bump.

## Source excerpt

So I had two bug reports about prefix in less than a week. It means several things, one of them is that my code is getting used in the wild, which is nice. The other side of the coin is that people do find bugs in there. This one is about the behavior of the btree opclass of the type prefix range. We cheat a lot there by simply having written one, because a range does not have a strict ordering: is [1-3] before of after [2-4]? But when you know you have no overlapping intervals in your prefix_range column, being able to have it part of a primary key is damn useful.