Commentary - PostgreSQL World @postgreSQLworld

Commentary - Daily PostgreSQL insights, tips, and questions to keep your knowledge sharp. Follow along to refresh your memory and learn something new every day! online Joined January 2018

Tweets

163
Followers

41
Following

364
Likes

288

Commentary - PostgreSQL World @postgreSQLworld

8 months ago

this is often unacceptable. It is possible to allow writes to occur in parallel with index creation, but there are several caveats to be aware of. Follow for more PostgreSQL related updates.

0 0 0 19 0

View Details

Commentary - PostgreSQL World @postgreSQLworld

8 months ago

Creating an index on a large table can take a long time. By default, PostgreSQL allows reads (SELECT statements) to occur on the table in parallel with index creation, but writes (INSERT, UPDATE, DELETE) are blocked until the index build is finished. In production environments...

1 0 0 24 0

View Details

Commentary - PostgreSQL World @postgreSQLworld

8 months ago

So remember: Next time your query returns weird results, check for the third state 🧐 Follow for more Postgresql related stuff.

0 0 0 14 0

View Details

Commentary - PostgreSQL World @postgreSQLworld

8 months ago

🎯 Bonus tip: Postgres automatically knows TRUE and FALSE are booleans, but not NULL since NULL could be text, int, date, etc. That’s why sometimes casting matters.

1 0 0 25 0

View Details

Commentary - PostgreSQL World @postgreSQLworld

8 months ago

Ever wondered why in PostgreSQL TRUE, t, yes, 1 all mean the same thing? 🤔 And why NULL isn’t just “false”? Let’s unpack how booleans really work in Postgres 🧵

1 0 0 30 0

View Details

Commentary - PostgreSQL World @postgreSQLworld

8 months ago

dropping legacy_tax_code pauses for 3ms (unnoticed), but a hung autovacuum ANALYZE queues it to 15s of stalled orders. Follow for more PostgreSQL stuff

0 0 0 21 0

View Details

Commentary - PostgreSQL World @postgreSQLworld

8 months ago

pile up, spiking timeouts and dropping TPS to near-zero. Storage reclamation defers too: physical data lingers until updates generate dead tuples (reclaimed gradually by autovacuum in write-heavy OLTP) or a forced rewrite compacts it. For example, in an e-commerce orders table,

1 0 0 28 0

View Details

Commentary - PostgreSQL World @postgreSQLworld

8 months ago

What will happen if, in a production PostgreSQL table with heavy read and write OLTP operations, a column that is not used in any queries is dropped?

1 0 0 37 0

View Details

Commentary - PostgreSQL World @postgreSQLworld

a year ago

Did you know PostgreSQL has a built-in pg_sleep() that can be used for fun query manipulations? SELECT 'Hello', pg_sleep(5), 'World!'; The query pauses for 5 seconds before returning results. Follow for more ❤️PostgreSQL❤️ related posts.