Old comment on forum: Migrating from #postgres 9.5 to 11+ is painful.
Me, migrating from 9.4 to 17.2 for several weeks: Huh, I didn't think about it...
Old comment on forum: Migrating from #postgres 9.5 to 11+ is painful.
Me, migrating from 9.4 to 17.2 for several weeks: Huh, I didn't think about it...
PostgreSQL, we've generally heard, is "good enough" for most intents and purposes.
We'd love to know what YOU think. What's stopped you from using #PostgreSQL in the past, and what solution did you choose instead? When have you opted for #Postgres where it turned out better than expected?
Databricks eyeing Neon for $1B shows big money betting on Postgres. This could reshape our database options.
#PostgreSQL #OpenSource #DevTools https://www.upstartsmedia.com/p/scoop-databricks-talks-to-acquire-neon
Wishing everyone a great time at PGConf.BE by volunteers starting today in UCLL - Campus Proximus in #Haasrode (Leuven), #Belgium
Find out more on https://foss.events/2025/05-06-pgconf-be.html
Official hashtag(s): #postgresql
What's new with Postgres at Microsoft? The 2025 edition of our annual blog post is now live.
Over the past year, the team at Microsoft who work on Postgres has contributed across multiple fronts:
New features in Azure Database for PostgreSQL - Flexible Server
Code contributions to Postgres 18 (including async I/O!)
Open source work on the Citus extension
Contributions to the Postgres open source community—things like @posetteconf, helping make @pgconfdev happen, the Talking Postgres #podcast, and sponsoring #PostgreSQL conferences around the globe
This year's blog post includes a hand-made infographic that maps out the major workstreams—plus highlights, explanations, links, and shout-outs to some of the many people behind the work.
If you care about PostgreSQL—as a user, contributor, or fan—I hope you'll give it a read.
Read the full blog post on Microsoft Tech Community: https://techcommunity.microsoft.com/blog/adforpostgresql/whats-new-with-postgres-at-microsoft-2025-edition/4410710
I'm very impressed how easy it is to use #OpenStreetMap data locally:
1. Download a subset of OSM on https://download.geofabrik.de/ for your country.
2. Use Osmium to filter by tags and export into a TSV.
3. Import the TSV into #PostgreSQL using a single \copy command.
4. Create a btree_gist index for #PostGIS geospatial and ordinary queries.
In less than 5 min, you're ready to run queries like "nearest restaurants around me" locally & fast!
Kudos for making it so simple, which is not easy. =)
In a short exchange with @jankatins I was stimulated to figure out a concise answer to needing to grab the previous or the upcoming non-null value in a column in PostgreSQL, in the order decided by the user, which would be similar to using `lead` and `lag` with the non-supported IGNORE NULLS directive.
The implementation I came up with nears poetry in its simplicity and elegance: https://gist.github.com/diraneyya/4455b69e034651151983228cd8b2114b
Can PostgreSQL really handle vector search for AI? Absolutely.
Watch Vladlen Popolitov share how PostgreSQL is evolving with new index types, data formats, and query strategies—enabling high-performance AI-powered search without needing to reshape your data at #PostgreSQLDayBangkok
Watch the full session on the FOSSASIA YouTube channel: https://youtu.be/nql66umVM0I
Deploy Java Like a Pro: Your First Quarkus App on OpenShift in Minutes
A fun, hands-on guide for Java developers to build a REST API with Quarkus, PostgreSQL, and deploy it to OpenShift Developer Sandbox
https://myfear.substack.com/p/quarkus-rest-api-openshift-postgresql-guide
#Quarkus #Java #OpenShift #PostgreSQL #Kubernetes
I'm gonna try #Svelte, with SSR, for also the backend. The database will be #postgresql with the GeoGis extension, since I'll be handling GPS data. The ORM will be #knex, a query builder with migration support.
All of course in #typescript ! With #bunjs.
After a month of serious use and study of PostgreSQL, I can say that I absolutely stand by this technology. It is rare that I found something that disappointed me.
Speaking of which, I find PostgreSQL's lack of support for the IGNORE NULLS behaviour on window functions to be quite unfortunate.
The #PostgreSQL upgrade (14->15) was shockingly easy on all three servers, which makes me wonder what horrors it has in store for me when I go to do the same thing on my work database servers, which have much more complicated access controls, replication, and other fun stuff like that.
After supper tonight, I'm going to try upgrading three #PostgreSQL "clusters" from 14 to 15. I don't think there are any anticipated gotchas, but that's why we do these things on little personal databases before taking a wrecking ball to prod.
Still going to have to research how to upgrade a "cluster" that is running streaming replication. That'll be a hassle for sure.
#PostgreSQL Event Calendar, Reminder:
Postgres Extensions Ecosystem Mini-Summit #5
Date: 2025-05-07T16:00:00Z - 2025-05-07T17:00:00Z
Location: https://meetu.ps/e/NW9JV/k17qn/i
ICS file: https://ics.postgresql.life/0cfkjr39kpb80mm07a6pdngm7shufiprti50o4c4am7u1dtd70u7p79b8d.ics
#PostgreSQL Event Calendar, Reminder:
Postgres Extensions Ecosystem Mini-Summit #5
Date: 2025-05-07T23:00:00Z - 2025-05-08T00:00:00Z
Location: https://meetu.ps/e/NW9JV/k17qn/i
ICS file: https://ics.postgresql.life/gconifb2gs6k3fl94srak87bu2d5esc3hn7tekqpurlj2u4pf1a2dppglr.ics
DB-Engines Ranking climbers of the month:
PandaDoc is hiring Senior Python Engineer (Growth)
#python #django #aws #docker #kafka #kubernetes #postgresql #redis #seniorengineer
Remote; Poland
Full-time
PandaDoc
Job details https://jobsfordevelopers.com/jobs/senior-python-engineer-growth-at-pandadoc-com-feb-13-2025-1a7eca?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
I guess I need to rewrite this query
#postgresql #pgadmin #testing
Some issues/tips with #AWS io1/io2 and #PostgreSQL replicas.
For io1/2 volumes on AWS you get provisioned IOPS and burst IOPS. If you read the fine print, MBpS throughput is computed based on provisioned IOPS, and works out to something like 1MBpS/80iops.
Think is, the walreceiver actually does relatively few IOPS but high MBpS because it's writing 16mb WAL segments and block flushes on tables. So you have to overprovision a lot. You've been warned!