CatOps
5.1K subscribers
94 photos
5 videos
19 files
2.69K links
DevOps and other issues by Yurii Rochniak (@grem1in) - SRE @ Preply && Maksym Vlasov (@MaxymVlasov) - Engineer @ Star. Opinions on our own.

We do not post ads including event announcements. Please, do not bother us with such requests!
Download Telegram
​​Уже не помню, что я гуглил, но в итоге нагуглил вот такою презентаху от Zalando о том, как и почему они разворачивали Postgres кластер в контейнерах и облаке

Кто работает с Postgres должно быть интересно (хотя бы на будещее)

#databases #postgres #docker
Шпаргалка по работе с Postgres

По ссылке примеры от простейших взаимодейсивий с таблицами до описания запросов для проверки активности БД и анализа статистики

#databases #postgres
Forwarded from Tech Cheat Sheet (Oleg Kovalov)
Learn from memes is a working strategy!

Therefore, I’d like to share with you this article (quite a long one) that describes a Postgres meme.

So, you could learn its concept broken down by a “level of depths”.

#databases #postgres
👍94
The Guardian tells a story of their migration into AWS Aurora Serverless.

This article doesn’t go too deep into technical aspects, but provides a nice overview of the issues one may encounter when trying to move to Aurora.

A couple of things that I found interesting:

- Whatever cloud migration tools are there, pg_dump and pg_restore are your trusted friends.

- This paragraph:


We’re spending roughly $220/month for storage and compute for the database. For the same price we could have rented a db.m7g.xlarge (16GB RAM, 4 vCPUs) Postgres instance along with 100GB of EBS storage or a db.r7g.large (16GB RAM, 2 vCPUs) Aurora instance. I suspect both of these options would have done the job for us, and maybe not have suffered from the same cold start problems as our serverless database, but after 3 migrations, it’s probably time to get back to doing some feature work!


#databases #postgres #aws
👍3🤔31😁1🤡1
Ok. I think I can start sharing things from FOSDEM / CfgMgmt Camp conferences.

To my knowledge, the videos are not available yet, but here are some pretty self-explanatory slides from the opening talk of the PostgreSQL panel: PostgreSQL Performance - 20 years of improvements.

In this talk, the author - a core contributor of PostgreSQL - presets the benchmark results of 10 major versions of PostgreSQL, so you can see how it evolved over the years.

A link to the talk page

#databases #postgres #fosdem
👍4
Another thing from FOSDEM PostgreSQL devroom is pgroll - a tool that allows one to execute zero-downtime (zero lock-time really) migrations in PostgreSQL.

Slides are available at the talk page. I hope, the video will be available soon as well. It was a very good talk!

#databases #postgres #fosdem
👍7
A great concise explainer-article about PostgreSQL.

It’s needless to say, how popular is Postgres in the industry. This article covers topics of:

- Connection management
- WAL
- MVCC
- Query execution
- Indexing
- Table partitioning
- Logical decoding
- Extensions
- Statistics collector

So, a quite excessive list actually. My only two nitpicks are:

- When talking about MVCC, there’s a phase that sounds as if locks do not exist in Postgres. They pretty much do! Moreover, it’s crucial to pay attention to what locks what operations acquire. I usually use this reference to double-check.
- When talking about the query planning, there’s article doesn’t explain the subtle difference between EXPLAIN and EXPLAIN ANALYZE. The latter actually runs a query under the hood, which may be ok for SELECT queries, but likely not for inserts and updates.

Apart from this small things, this is a very good article!

#databases #postgres
👍13
Figma has replaced PGBouncer with their own implementation called PGKeeper written in Go as a connection pooler for Postgres.

I really enjoyed this article, because they go into the implementation depths and describe why certain decisions were taken. Unfortunately, it doesn't always happen in such articles. Also, this is a nice reminder that software engineering is not only about writing CRUDs.

Unfortunately, they do not plan to open source it for now, also because it's too tightly coupled with libraries and approaches Figma uses internally. To be honest, it makes sense for in-house software to aim to one's specific needs rather than being generic enough to be open sourced.

#databases #postgres
👍4😁4