Oracle Has Adopted Boolean in 23ai and Postgresql Had It Forever
Posted2 months agoActive2 months ago
hexacluster.aiTechstory
calmmixed
Debate
40/100
Database ManagementOraclePostgresql
Key topics
Database Management
Oracle
Postgresql
Oracle's adoption of a native BOOLEAN data type in 23ai is compared to PostgreSQL, which has had it forever, sparking discussion on database features and compatibility.
Snapshot generated from the HN discussion
Discussion Activity
Moderate engagementFirst comment
1h
Peak period
6
0-2h
Avg / period
3.6
Comment distribution18 data points
Loading chart...
Based on 18 loaded comments
Key moments
- 01Story posted
Oct 29, 2025 at 10:51 AM EDT
2 months ago
Step 01 - 02First comment
Oct 29, 2025 at 12:06 PM EDT
1h after posting
Step 02 - 03Peak activity
6 comments in 0-2h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 30, 2025 at 4:07 AM EDT
2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45747605Type: storyLast synced: 11/20/2025, 1:17:51 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
But last time I really used Oracle's RDBMS (10g era) it still had capabilities that no open source database had. If you really needed that, there wasn't an easy substitute. I'm sure Postgres has narrowed the gap by now.
I am sure some day it would come. But it will likely take another 10 years. I just hope Neki + Oriole could come sooner.
Source:
Enterprise has its own needs largely irrelevant to the rest of us.
It is possible that there are simple solutions to these problems, but the perception that they are serious will turn companies away from a migration.
The main reason I'd say is that there's no functional benefit to ripping out a database and replacing it, so there's always something more important to do that actually drives revenue.
I'd argue that postgres brings with it substantially lower risks in terms of license compliance/audits/price hikes. Not sure if that can drive a migration, but it should be reason enough to select open source for new projects.
BUT Oracle has some killer features that PG just doesn’t. The first that comes to mind is for-real multi-master. Close second is declaring partitions in the DDL of the table itself.
Oracle's tradition of tacking on $CURRENT_TREND suffixes to its DB versions is, has always been, and will always be cringy. What has it been? i for internet, g for grid, c for cloud, and now ai?
I’m glad to see this internet debate finally concluded.