Databases are hard. We make them faster. ⚡ Deep dives on optimization, open source advocacy, and expert peer support. Stay portable: percona.community
Joined September 2019
- Tweets 4,806
- Following 4,455
- Followers 7,121
- Likes 3,909
2,219 Photos and videos
PostgreSQL 18 ships native OAuth 2.0 but delegates token validation to external libraries — every IdP implements OIDC slightly differently.
Step-by-step: PingOne pg_oidc_validator, device flow login, working psql connection.
percona.community/blog/2026/… - LC
#PostgreSQL #OIDC
1
48
A few hours. Some TypeScript. A Slack token already sitting on a laptop.
That's what it took to build a bot that reads every DM, replies in your voice, and deflects if asked whether it's human. No admin approval. No OAuth app. No review.
percona.community/blog/2026/… - LC
#AISecurity
57
innodb_redo_log_capacity set to a default years ago and never touched? You're guessing.
Watch Innodb_log_waits. Measure LSN growth. Size for 30–60 min of peak redo, not a % of RAM.
percona.community/blog/2026/… - LC
#MySQL #InnoDB
36
Meet the team behind this account. Five of us, one shared inbox, and a habit of turning up at every database conference going. Each post is signed with our initials so you know who you're talking to.
percona.community/blog/2026/…
— LC #Postgres #Community #mySQL #valkey #database #devs
42
"70% of RAM" isn't tuning. It's a starting guess.
A 99% hit ratio doesn't mean healthy — you can be IO-bound at 99%. Watch free buffers, dirty page %, and the rate of change on Innodb_buffer_pool_reads.
percona.community/blog/2026/… - LC
#MySQL #InnoDB
28
You debugged something gnarly in production this year. We'll pay you $350 to write it up.
Your voice, your hard-won experience, your name on the byline. Pitch us a topic and we'll work with you on the rest.
percona.community/blog/2026/… - LC
#OpenSource #DBA #Developers #engineering
48
1 TB database, 2% daily change rate. Six daily fulls = 6 TB. One full six incrementals ≈ 1/5 of that.
Percona Operator for MySQL 1.1.0 ships incremental backups. LSN-tracked, chain-aware rotation, cascade delete.
percona.community/blog/2026/… - LC
#MySQL #Kubernetes
34
FATAL: OAuth bearer authentication failed in your PostgreSQL 18 log on a successful login? Not a real error — side effect of how OAuth bootstraps.
A field guide to actual OIDC failures: issuer mismatch, expired tokens, scope misses percona.community/blog/2026/… LC
#PostgreSQL #OIDC
51
Want to discuss open-source databases? 🚀 Request to join the Percona Community LinkedIn group to share your knowledge and grow with us! 👇 - LC
linkedin.com/groups/2299033/
#Percona #Database #OpenSource #TechCommunity #MySQL #PostgreSQL #MongoDB #DevOps
1
1
107
Forks and closed alternatives weren't the answer for pgBackRest. Continuity was.
A look at how cross-ecosystem funding, engineering, and a broader maintainer base are keeping it open and healthy:
percona.com/blog/keeping-pgb… -- LC
#PostgreSQL #pgBackRest #OpenSource
1
95
From Open Source Summit to Percona Live! Kyle Flanagan shares all you need to know about Percona Live as the team winds down Open Source Summit.-- KF
1
1
106
Got your ticket for Percona Live next week? Come join us to hear fantastic speakers—and try to snag one of our limited Goat plushies! See the agenda: perconalive.com/2026-usa/tal… Use 𝐏𝐄𝐑𝐂𝐎𝐍𝐀𝟕𝟓 for a 75% discount when you register!
1
52
Automated tools are great, but manually migrating hash slots in a Valkey/Redis cluster gives you total control during live maintenance. Learn how to manage MIGRATING states, move keys, and update routing tables safely.
percona.com/blog/manually-mi… #Valkey #Redis #DevOps #Database LC
79
Packing for @PGConfdev, what's the right shirt for day one: PGConf.dev 2025, oldest @PostgreSQL event shirt that still fits (EU 2018), some other OSS event?
AT
1
1
74
Percona Community retweeted
Honest question for DBAs and devs: How far do you actually let an AI coding agent into your database work?
No judgement. We just want to know where the community line is.
50%
Read-only / SELECTs
0%
Writes to dev only
0%
Writes to prod w/ review
50%
Not touching my DB
2 votes • Final results
3
1
440
Two teams. Same problem. Built independently.
pginbox.dev is joining hackorum.dev — one project to make the pg-hackers mailing list actually readable. This is what open source is supposed to feel like. percona.community/blog/2026/… #Postgres
#Community
62
28% of organizations use open source but contribute nothing back.
Not a moral problem. A business one.
Non-contributors spend ~$670k/year building internal workarounds for things upstream already shipped & hear about breaking changes last.
devops.com/open-source-contr… LC
38
If your innodb_redo_log_capacity is set to a % of RAM, you're guessing.
Redo sizing is about LSN growth rate, not memory. Measure 30–60 minutes of peak redo generation and size for that.
What's your current capacity — and do you know your redo/hour?
percona.community/blog/2026/… LC
46
Meet the team behind this account. Five of us, one shared inbox, and a habit of turning up at every database conference going. Each post is signed with our initials so you know who you're talking to.
percona.community/blog/2026/…
— LC
2
3
186