# hstore

Published articles for hstore.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Old tech is sometimes better - a case study based on blogpost from Now-Next...

DevFeed: [Old tech is sometimes better - a case study based on blogpost from Now-Next...](<https://devfeed.tech/articles/old-tech-is-sometimes-better-a-case-study-based-on-blogpost-from-now-next-88510.md>)

Original publisher: [Read original article](<https://www.depesz.com/2026/10/16/old-tech-is-sometimes-better-a-case-study-based-on-blogpost-from-now-next/>)

Author: depesz

Published: 2026-10-16T10:09:03Z

Content type: article

Language: en

Sources: [select \* from depesz;](<https://devfeed.tech/sources/select-from-depesz.md>)

Topics: [table-partitioning](<https://devfeed.tech/topics/table-partitioning.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [changes](<https://devfeed.tech/tags/changes.md>), [hstore](<https://devfeed.tech/tags/hstore.md>), [jsonb](<https://devfeed.tech/tags/jsonb.md>), [logging](<https://devfeed.tech/tags/logging.md>), [now-next](<https://devfeed.tech/tags/now-next.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [reaction](<https://devfeed.tech/tags/reaction.md>), [trigger](<https://devfeed.tech/tags/trigger.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

The author benchmarks PostgreSQL trigger-based change logging using JSONB and hstore, comparing full-row logging with logging only changed columns. In the reported tests, hstore is faster and uses somewhat less disk space, with diff logging faster than full-row logging. The author cautions that hstore is not necessarily better for every use case.

### Source excerpt

Some time ago I read this blogpost. They wrote about logging changes to table using a trigger, but one thing that caught my attention was: Storing only the changed columns made the log five times smaller and the trigger slower. Figured I can try it myself... Unfortunately they didn't provide schema of table, nor test ... Continue reading "Old tech is sometimes better - a case study based on blogpost from Now-Next..."

## Postgres Datatypes - The ones you're not using.

DevFeed: [Postgres Datatypes - The ones you're not using.](<https://devfeed.tech/articles/postgres-datatypes-the-ones-you-re-not-using-41168.md>)

Original publisher: [Read original article](<https://www.craigkerstiens.com/2014/05/07/Postgres-Datatypes-The-ones-youre-not-using./>)

Author: Map

Published: 2014-05-07T20:55:56Z

Content type: article

Language: en

Sources: [Craig Kerstiens](<https://devfeed.tech/sources/craig-kerstiens.md>)

Topics: [data type](<https://devfeed.tech/topics/data-type.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [arrays](<https://devfeed.tech/tags/arrays.md>), [database](<https://devfeed.tech/tags/database.md>), [extension](<https://devfeed.tech/tags/extension.md>), [gin](<https://devfeed.tech/tags/gin.md>), [gist](<https://devfeed.tech/tags/gist.md>), [hstore](<https://devfeed.tech/tags/hstore.md>), [indexes](<https://devfeed.tech/tags/indexes.md>), [key-value-store](<https://devfeed.tech/tags/key-value-store.md>), [migration](<https://devfeed.tech/tags/migration.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [range](<https://devfeed.tech/tags/range.md>), [text](<https://devfeed.tech/tags/text.md>), [timestamps](<https://devfeed.tech/tags/timestamps.md>), [timezone](<https://devfeed.tech/tags/timezone.md>), [types](<https://devfeed.tech/tags/types.md>)

### AI overview

The excerpt recommends several PostgreSQL types for specific needs: hstore stores optional key-value data without adding columns and can use GIN or GiST indexes, but requires an extension; range types can constrain intervals to prevent overlaps; and timestamptz supports timezone conversion. It presents UUIDs as potentially useful for large applications where integer keys may cause scaling or sharding problems. The text describes indexed binary JSON as upcoming in PostgreSQL 9.4, while cautioning against money because it assumes one currency and has caveats compared with numeric. Arrays, interval, ISN, and inet are briefly listed as other options.

### Source excerpt

Postgres has a variety of datatypes, in fact quite a few more than most other databases. Most commonly applications take advantage of the standard ones - integers, text, numeric, etc. Almost every application needs these basic types, the rarer ones may be needed less frequently. And while not needed on every application when you do need them they can be an extremely handy. So without further ado let's look at some of these rarer but awesome types. hstore Yes, I've talked about this one before, yet still not enough people are using it. Of this list of datatypes this is one that could also have benefit for most if not all applications. Hstore is a key-value store directly within Postgres. This means you can easily add new keys and values (optionally), without haveing to run a migration to setup new columns. Further you can still get great performance by using Gin and GiST indexes with them, which automatically index all keys and values for hstore. It's of note that hstore is an extension and not enabled by default. If you want the ins and outs of getting hands on with it, give the article on Postgres Guide a read. Range types If there is ever a time where you have two columns in your database with one being a from, another being a to, you probably want to be using range types. Range types are just that a set of ranges. A super common use of them is when doing anything with calendaring. The place where they really become useful is in their ability to apply constraints on those ranges. This means you can make sure you don't have overlapping time issues, and don't have to rebuild heavy application logic to accomplish it. Timestamp with Timezone Timestamps are annoying, plain and simple. If you've re-invented handling different timezones within your application you've wasted plenty of time and likely done it wrong. If you're using plain timestamps within your application further there's a good chance they dont even mean what you think they mean. Timestamps with timezone o

## The missing PostgreSQL documentation

DevFeed: [The missing PostgreSQL documentation](<https://devfeed.tech/articles/the-missing-postgresql-documentation-41149.md>)

Original publisher: [Read original article](<https://www.craigkerstiens.com/2013/08/07/The-missing-PostgreSQL-documentation/>)

Author: Map

Published: 2013-08-07T20:55:56Z

Content type: opinion

Language: en

Sources: [Craig Kerstiens](<https://devfeed.tech/sources/craig-kerstiens.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [analysts](<https://devfeed.tech/tags/analysts.md>), [application](<https://devfeed.tech/tags/application.md>), [blog](<https://devfeed.tech/tags/blog.md>), [contributing](<https://devfeed.tech/tags/contributing.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [functions](<https://devfeed.tech/tags/functions.md>), [guide](<https://devfeed.tech/tags/guide.md>), [guides](<https://devfeed.tech/tags/guides.md>), [hstore](<https://devfeed.tech/tags/hstore.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [python](<https://devfeed.tech/tags/python.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [types](<https://devfeed.tech/tags/types.md>), [usability](<https://devfeed.tech/tags/usability.md>)

### AI overview

The author argues that PostgreSQL's reference documentation is thorough, but its learning support is weak: the tutorial is buried in a roughly 2,000-page manual, and newcomers may not know where to start or recognize feature names such as hstore and PLV8. They propose rebuilding the tutorial and creating guides for database beginners, application developers, DBAs, and SQL and reporting users. The excerpt also suggests contributing to postgresguide.com or submitting guest posts; it ends during a call for input, so it does not establish what happened next.

### Source excerpt

For a couple of years I've complained about the Postgres documentation and at the same time paraded it as one of the best sets of documentation I've encountered. In many ways the reason I veer towards Postgres as well as Python and Django is the quality of their documentation. If you need to find details about something its documented, and more importantly well and thoroughly documented. In large part I came to Python by happenstance through Django, and Postgres through happenstance of an employer. Yet, Django was very little of an accident. The Django Tutorial got me a large part of what I needed to know and more excited about development than I had been in some time. Python has done some work at adding docs to make this even better, sadly its still very much needed for PostgreSQL. Whats Missing in the Postgres Docs Theres a huge variety of types of documentation, off the top of my head theres: Reference docs (Postgres excels at this) Onboarding (Postgres tutorial huh?) Tailored guides (Postgres? I can haz? Nope... We don't understand....) Postgres is great if you know the name of what you're looking for, but if you don't you're entirely left in the dark. Understanding the power of Postgres Postgres is good enough at performance, good enough at usability, and awesome at how powerful and flexible it can be. But all of this is entirely lost if you have to know the esoteric name of what you're looking for. What the hell is an hstore... In so many ways KVstore makes infintely more sense. In the same sense PLV8, I have to know not only what PL stands for but V8 as well, versus the JavaScript extension for Postgres. I understand there are plenty of reasons why some of these things are the way they are, but its also limiting how great the broader perception is. Postgres externally is this hard to use DB, that well is just a database, versus giving developers a set of powerful and useful functions to make their lives better. The Solution Lets fix things, there are a ton of peopl