andatki

6 ms·

1.
by andatki 21d ago
Author here. Happy to discuss any points in the post and appreciate feedback, thanks.
2.
by andatki 3mo ago
Happy to discuss any details from the post. Thanks for taking a look.
3.
Christmas Outage to #1 App Store Ranking: An Aura Frames Postgres Scaling Retro(andyatkinson.com)
7 points by andatki 3mo ago|1 comments
4.
by andatki 8mo ago
https://andyatkinson.com
5.
by andatki 9mo ago
If merging or moving data between environments is a regular occurrence, I agree it would be best to have non-colliding primary keys. I have done an environment move (new DB in different AWS region) with integers and sequences for maybe a 10
6.
by andatki 9mo ago
Great!
7.
by andatki 9mo ago
Good addition!
8.
by andatki 9mo ago
This was written based on working on several Postgres databases at different companies of “medium” size as a consultant, that had excessive IO and latency and used UUID v4 PKs/FKs. They’re definitely out there. We could transform the s
9.
by andatki 9mo ago
Appreciate it!
10.
by andatki 9mo ago
Note that if you’re using UUID v4 now, switching to v7 does not require a schema migration. You’d get the benefits when working with new records, for example reduced insert latency. The uuid data type supports both.
11.
by andatki 9mo ago
Hi there. Thanks for the feedback. I updated that section to hopefully convey the intent more. The type of ordering we care about for this topic is really B-Tree index traversal when inserting new entries and finding existing entries (singl
12.
by andatki 9mo ago
Good point that the post should be made clear it’s referring only to my experience with Postgres.
13.
Tip: Put your Rails app on a SQL query diet(andyatkinson.com)
4 points by andatki 1y ago|0 comments
14.
Big Problems from Big in Lists with Ruby on Rails and PostgreSQL(andyatkinson.com)
3 points by andatki 1y ago|0 comments
15.
by andatki 2y ago
I’ve used Marp a lot and it’s great. Column layouts and code highlighting are two features Presenterm offers that I don’t think are available in Marp.
16.
by andatki 2y ago
What sorts of skills are you looking to build? Since this post has a lot of comments about query optimization, I’d suggest query optimization is more in the realm of developers and not DBAs. Schema, query, and index design. DBAs might be mo
17.
Django and Postgres for the Busy Rails Developer(andyatkinson.com)
2 points by andatki 2y ago|0 comments
18.
by andatki 2y ago
Nice post covering many of the main ways to improve efficiency. Here’s a related post I wrote for AppSignal: What's Coming in Ruby on Rails 7.2: Database Features in Active Record https://blog.appsignal.com/2024/07
19.
PostgreSQL 17: JSON_table(), Merge with Returning, and Updatable Views(andyatkinson.com)
2 points by andatki 2y ago|0 comments
20.
Solid Cache for Rails and PostgreSQL(andyatkinson.com)
3 points by andatki 2y ago|1 comments
21.
Trying Out Solid Queue and Mission Control with PostgreSQL(andyatkinson.com)
3 points by andatki 2y ago|0 comments
22.
by andatki 2y ago
What a name! - A dot Atkinson
23.
by andatki 2y ago
Rails and Postgres (and AWS) was the pre-acquisition stack, and development continued with that stack during this time period (2020-2021). https://en.wikipedia.org/wiki/Flip_(software) Microsoft acquired companies with
24.
by andatki 2y ago
Hi there! That's funny! This interview and those gem updates were unrelated. However both are part of the sweet spot for me of education, advocacy, and technical solutions for PostgreSQL and Ruby on Rails apps. I hope you’re able to ch
25.
by andatki 2y ago
Great list of Postgres features called out that highlight the extensive feature set. Most of these are covered in my book, for anyone that’s interested in learning them. The book uses a Ruby on Rails app with Postgres instances for examples
26.
by andatki 2y ago
Newer versions of Postgres also support dropping indexes concurrently. I recommend using the concurrently option when dropping unused or unneeded indexes on any table with active writes and reads. https://www.postgresql.org/
27.
by andatki 2y ago
Makes sense. Check out the implementation of automatic lock timeout retries in Strong Migrations. Lock Timeout Retries [experimental] https://github.com/ankane/strong_migrations
28.
by andatki 2y ago
Do you do any alerting for INVALID indexes? For example, by default PgHero will display them prominently and I believe PgAnalyze does as well. My thought is to put the energy into making INVALID indexes highly visible. Perhaps combined with
29.
by andatki 2y ago
Hey Shayon. IF NOT EXISTS or the Active Record version "if_not_exists: true" can be pretty handy though when there's a valid index in production, to help drive schema definition consistency in all environments (prod, dev, CI,
30.
by andatki 2y ago
Author here! If you use PostgreSQL with web apps, what sorts of things surprised you as functionality that was useful, that you didn't initially know about? Or maybe, what functionality was more complex than you expected? Thanks!

More ›