Details about the talk: We ran everything in a single-tier AWS setup, and it worked, until the technical debt caught up. This talk covers why we moved to a 3-tier architecture, how we migrated PostgreSQL (RDS) and Redis (ElastiCache) with zero down. Read more on the Luma page.

Jom, First talk from CoinGecko's SRE!.​.Flat Was Fast. 3-Tier Helped Us Grow. But You Probably Don't Need it. Yet by Taqwa, Senior SRE. ​.Other presentations:.- Future of AI in Software Testing.- Harmony between Agile and Testing.​.Don't forget to RSVP

Powered by Ai.

Jeng, dah jual. Follow me to cepat profit. When I sell, you buy.

Kalau spike macam ni, cuba add index, biasa akan turun terus lepas tu. Run CREATE INDEX on rumah(total).

Hari ni saya bazir masa setup balik integration.- Neovim.- Tmux.- Ghostty (baru). Dah malas pakai Wezterm yang ada beberapa kekurangan.

Member tengah cari dev. Fully remote, 15k per month

RT @QuentinAnthon15: Third, it's super easy to get distracted in the downtime while LLMs are generating. The social media attention economy….

Jom!.

Jom!. Syaah Mohd Fauzi (MZR Global).The Vocket: From start to finish, the untold story. 🎟️

RT @hlmshkr: husein is really goated ML engineer/researcher, i hope bro will be given opportunity by malaysian gov to advise education syst….

I might write a blog post on how to sync with Rails schema too. Hint: The challenge is running the queries manually, then, back populate the changes to Rails schema. As always, there's a trade off when you are not using the default. That's all for now, thanks for reading. 8/8.

pg_partman might help in this case, but I don't have experience using it yet:. SELECT partman.apply_to_all(. 'cars',. 'CREATE INDEX CONCURRENTLY % ON %s (colour_id, created_at, price)');. Right now, getting the index up and running is more important. 7/8.

Adding the index to the parent table will ensure newly created partition will have the same index as other partitions. There are some complications regarding the index naming and I'm still looking into it, but there are several articles about it. 6/8.

(3) Attach the partition to the parent table to the parent index. ALTER INDEX idx_test ATTACH PARTITION cars_201701_test_idx. This will ensure the index on the parent table will be valid. We also have to do it manually for every partition which is another pain. 5/8.

(2) Add index to all the partitions. CREATE INDEX CONCURRENTLY cars_201701_test_idx ON cars_201701 (colour_id, created_at, price);. We can now create the index concurrently and not worry about table being locked. However, we have to do it for every partition. 4/8.

(1) Add index to the parent table. CREATE INDEX idx_test.ON ONLY cars (colour_id, created_at, price);. If you run \d cars, you'll notice the index is marked as INVALID and that's ok for now. 3/8.

I'll cut the story short, but in order to achieve similar objective, we have to do things differently. Basically:. 1) Add index to the parent table.2) Add index to all the partitions.3) Attach the partition to the parent table. 2/8.

TIL after I tried to add index to my Postgres partitioned table. Normally, we'll use CONCURRENTLY for the index creation to prevent exclusive lock on the table. This is useful for us to add an index on Production's DB. However, you can't with partitioned table. 1/8.

RT @afrieirham_: made my day, use now