Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

196
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#postgresql

15 posts15 participants0 posts today
*
arabiccola

A more useful version of NULLIF, in my opinion, is VALUEIF, it gives you back the equivalent value of all of its params. If the params differ from one another, then it returns NULL.

It is succinct and written poetically, just like `coalesce_equal`

gist.github.com/diraneyya/9455

`coalesce_equal(...)` is a PostgreSQL function that is similar to `coalesce`, but requires that all non-null arguments be equal for it to return the identical value, when not equal or all arguments...
Gist`coalesce_equal(...)` is a PostgreSQL function that is similar to `coalesce`, but requires that all non-null arguments be equal for it to return the identical value, when not equal or all arguments are null, it returns null.`coalesce_equal(...)` is a PostgreSQL function that is similar to `coalesce`, but requires that all non-null arguments be equal for it to return the identical value, when not equal or all arguments...
#postgresql#sql#utility
Stefan Fercot

Today I learned about the Year 2038 problem, basically Y2K's lesser-known cousin 🤦‍♂️👾

On 19 January 2038, some computers will run out of space to count time (because they store time as a 32-bit integer)⏳💾
Result: clocks roll over into negative numbers, and software may think it's 1901 🕰️➡️🙃
Plenty of time to fix… right? 🛠️🐛

🔗 en.m.wikipedia.org/wiki/Year_2

Thanks @mmeent_pg for dropping that gem on the #PostgreSQL slack! 🙌 :postgresql:

#TIL #TimeTravelBug #2038Oops 🚀🌀

en.m.wikipedia.orgYear 2038 problem - Wikipedia
Mad A. Argon :qurio:

Invincible #Postgres Saga, episode 3...

(At least this didn't happen on production :blobCat_giggle:)

Earlier this week I tried to do some tests on my "wonderful" misconfigured testing environment. I had some errors here and there and they had to reveal themselves during my experiment...
To make everthing up-to-date I had to refresh data in my app, which uses #Patroni #Postgresql database. Of course it crashed when I tried to do it. It didn't turn down whole cluster, only that one server, and in theory it still had normal API access. I expected it to come back quickly after I fixed things breaking my servers. But for some reason it couldn't. It didn't even try, at least in any visible way.
Seriuosly it was the most disturbing thing there :blobcatsweat: It should try to do something, right?!?
I tried to restart services in panic, without any result. It was late and I finished work for that day. Tired and worried I had to leave it stuck in "cannot reach consistent state" stage.

Next day I thought about doing force reinit or something to move it. But when I log into that server... Everything just worked :neofox_scream_stare_256:
I checked logs... Almost nothing special, just like database was stuck and after ~14 hours suddenly started working. Only one line telling backup was restored.
Damn, what backup?!? Why I don't understand what it did?!? And why it needed so much time?!?

At least I had working environment and didn't had to wonder what to do. Maybe my first chaotic attempts to force it to work did more harm than good and I should just leave it...

Someone should write in docs, which API status means "just leave me alone, trying to fix things" :neofox_think_derp: It would be easier.

#sysadmin#admin#IT
Cari

It's Debian upgrade season, which means that I had a whole lot of PostgreSQL database tidying to do this week! Fun! (It isn't.) In which I try to figure out how to make this process suck less two years from now:

lilacpixel.space/fixing-postgr

lilacpixel.spaceFixing PostgreSQL Collation Version Mismatches in Docker - lilacpixel.spaceA slightly quicker way of tidying your Docker-ized PostgreSQL databases.
#blog#PostgreSQL#Docker
Gael

Our new website is up: foss4g.be
The full program for the 2025 edition is now online:
foss4g.be/en/schedule
Tickets are available on a "pay what you want" basis:
shorturl.at/cCpR6
If the lack of a 0€ ticket option is a problem, just let us know—we’ll make it work.
Thanks to everyone who contributed to this project.
See you at FOSS4G Belgium 2025!
#FOSS4GBE2025 #PostgreSQL
#PostGIS #osgeobe #QGIS

Replied in thread
*
Debacle

@daniel @elbast

Es gibt leider nicht viele Providers für #email und #XMPP aus einer Hand. Ist schön, wenn's das gibt, auch weil es den use case "email address == JID" meistens einfacher machen dürfte.

Da der Aufwand für #ejabberd maintenance fast nur aus normalen package updates besteht (naja, ich habe gestern ein bisschen mit einer #Mnesia-to-#PostgreSQL migration gekämpft), wäre es schon klasse, wenn @mailbox_org das weiter anböte, aber mit modernen features wie occupant id, A/V calls usw.

Floor Drees

Rotterdam internet friends!! I'm looking for a venue for a #PostgreSQL meetup, September 11. Can your company host us, or do you know any affordable venues (budget is max 1800), please let me know? 🙏

Carsten Hoffmann

We have now switched the base image of our postgresql-partman-container over to the official postgres docker image. The chance was necessary because the #bitnami images are no longer available for free. Read more about it in the issue and the linked PR: github.com/dbsystel/postgresql

As of bitnami/containers#83267, starting today, bitnami images are moved to a 'bitnamilegacy' namespace, and new images are created in 'bitnamisecure'. We need to switch to this new namespace.
GitHubHandle deprecation of bitnami images · Issue #31 · dbsystel/postgresql-partman-containerBy jschirrmacher
#OpenSource#PostgreSQL#container
TrendingLive feeds
About