Gülçin Yıldırım J.
@apatheticmagpie.bsky.social
Postgres, books and more.
“For most of history, anonymous was a woman.”
“For most of history, anonymous was a woman.”
Reposted by Gülçin Yıldırım J.
Then on the main track Esther Minano & Ahmet Gedemenli dive into anonymization and Gulcin on Postgres 18 constraints.
Get the schedule: www.postgresql.eu/events/pgcon...
Get the schedule: www.postgresql.eu/events/pgcon...
PGConf.EU 2025 Schedule
PGConf.EU 2025 Schedule
www.postgresql.eu
October 17, 2025 at 3:38 PM
Then on the main track Esther Minano & Ahmet Gedemenli dive into anonymization and Gulcin on Postgres 18 constraints.
Get the schedule: www.postgresql.eu/events/pgcon...
Get the schedule: www.postgresql.eu/events/pgcon...
Reposted by Gülçin Yıldırım J.
If you want to understand Postgres locks beyond the basics, this talk is for you.
Catch it today at PGDay Austria! 🔒🐘
📍 14:10 – 14:55
📍 Room: Sophie
🗓️ Full schedule: pgday.at/schedule/
Catch it today at PGDay Austria! 🔒🐘
📍 14:10 – 14:55
📍 Room: Sophie
🗓️ Full schedule: pgday.at/schedule/
September 4, 2025 at 8:48 AM
If you want to understand Postgres locks beyond the basics, this talk is for you.
Catch it today at PGDay Austria! 🔒🐘
📍 14:10 – 14:55
📍 Room: Sophie
🗓️ Full schedule: pgday.at/schedule/
Catch it today at PGDay Austria! 🔒🐘
📍 14:10 – 14:55
📍 Room: Sophie
🗓️ Full schedule: pgday.at/schedule/
Reposted by Gülçin Yıldırım J.
ACCESS EXCLUSIVE is the strictest lock, blocking everything.
More pro tips:
Don’t mix strong-lock DDL with other operations in the same transaction.
Use lock_timeout to prevent cascading lock queues + handle retries gracefully.
Locks aren’t about security → they’re about concurrency control.
More pro tips:
Don’t mix strong-lock DDL with other operations in the same transaction.
Use lock_timeout to prevent cascading lock queues + handle retries gracefully.
Locks aren’t about security → they’re about concurrency control.
September 4, 2025 at 8:47 AM
ACCESS EXCLUSIVE is the strictest lock, blocking everything.
More pro tips:
Don’t mix strong-lock DDL with other operations in the same transaction.
Use lock_timeout to prevent cascading lock queues + handle retries gracefully.
Locks aren’t about security → they’re about concurrency control.
More pro tips:
Don’t mix strong-lock DDL with other operations in the same transaction.
Use lock_timeout to prevent cascading lock queues + handle retries gracefully.
Locks aren’t about security → they’re about concurrency control.
Reposted by Gülçin Yıldırım J.
But here’s the catch → MVCC doesn’t protect you from object locks. That’s where things get interesting.
🔑 Key takeaways:
MVCC avoids many issues, but DDL still needs strong locks.
Each DDL command has its own lock strength, some block both reads and writes.
🔑 Key takeaways:
MVCC avoids many issues, but DDL still needs strong locks.
Each DDL command has its own lock strength, some block both reads and writes.
September 4, 2025 at 8:47 AM
But here’s the catch → MVCC doesn’t protect you from object locks. That’s where things get interesting.
🔑 Key takeaways:
MVCC avoids many issues, but DDL still needs strong locks.
Each DDL command has its own lock strength, some block both reads and writes.
🔑 Key takeaways:
MVCC avoids many issues, but DDL still needs strong locks.
Each DDL command has its own lock strength, some block both reads and writes.
Reposted by Gülçin Yıldırım J.
In this session, Gülçin will explain how PostgreSQL handles table-level locks, especially those triggered by DDL operations.
It all starts with Postgres’ secret weapon: MVCC.
MVCC = Multi-Version Concurrency Control.
✅ Reads don’t block writes.
✅ Writes don’t block reads.
It all starts with Postgres’ secret weapon: MVCC.
MVCC = Multi-Version Concurrency Control.
✅ Reads don’t block writes.
✅ Writes don’t block reads.
September 4, 2025 at 8:46 AM
In this session, Gülçin will explain how PostgreSQL handles table-level locks, especially those triggered by DDL operations.
It all starts with Postgres’ secret weapon: MVCC.
MVCC = Multi-Version Concurrency Control.
✅ Reads don’t block writes.
✅ Writes don’t block reads.
It all starts with Postgres’ secret weapon: MVCC.
MVCC = Multi-Version Concurrency Control.
✅ Reads don’t block writes.
✅ Writes don’t block reads.
