Neues vom PostgreSQL Planet
Mankirat Singh: .abi-compliance-history file in PostgreSQL source?
Hubert 'depesz' Lubaczewski: Do you really need tsvector column?
Josef Machytka: PostgreSQL 18 enables data‑checksums by default
As I explained in my talk on PostgreSQL Conference Europe 2025, data corruption can be silently present in any PostgreSQL database and will remain undetected until we physically read corrupted data. There can be many reasons why some data blocks in tables or other objects can be damaged. Even modern storage hardware is far from being infallible. Binary backups done with pg_basebackup tool – which is very common backup strategy in PostgreSQL environment – leave these problems hidden. Because they do not check data but copy whole data files as they are.
Radim Marek: Beyond Start and End: PostgreSQL Range Types
One of the most read articles at boringSQL is Time to Better Know The Time in PostgreSQL where we dived into the complexities of storing and handling time operations in PostgreSQL. While the article introduced the range data types, there's so much more to them. And not only for handling time ranges.
Cornelia Biacsics: Contributions for week 44, 2025
PostgreSQL received attention through the following contributions at Data Stack Conf 2025 on Oct 29, 2025:
Speaker
- Radoslav Stanoev
- Pavlo Golub
- Lætitia Avrot
- Valeria Bogatyreva
- Devrim Gündüz
PostgreSQL Booth Staff
- Devrim Gündüz
- Pavlo Golub
Gabriele Quaresima spoke at Cloud Native Bergen on Tuesday, October 28, 2025.
Dave Stokes: Migration From MySQL To PostgreSQL In Five Steps Using DBeaver
I wrote a post in my MySQL blog on migrating from MySQL to PostgreSQL using DBeaver. You can pass it along to your acquaintances who want to get off the Dolphin and on the Elephant.
Not only will DBeaver move your tables and data, but you can compare them afterwards. In the post, I outline the process in five steps. DBeaver will let you do it in four.
Seiten
- « erste Seite
- ‹ vorherige Seite
- …
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14

