shayonj

11 ms·

151.
by shayonj 2y ago
Nice article, I was hoping for more content around Rack 3 since the intro of the article touches on it.
152.
by shayonj 2y ago
Nice! Love the direction
153.
Stream, transform, and route PostgreSQL data in real-time (early build)(github.com)
1 points by shayonj 2y ago|0 comments
154.
by shayonj 2y ago
I pushed out the v1. More deets at: https://github.com/shayonj/pg_flo/blob/main/pkg/routing/READ...
155.
by shayonj 2y ago
Very interesting, I have wanted to solve this issue for a while and it actually overlaps with the "routing" feature for pg_flo that I am working on. Basically you can make map what data gets routed to what table and column in the
156.
by shayonj 2y ago
Here is a simple example [1] where you can setup a replication for to send data for events tables where tenant_id = `3`. You can setup multiple groups, where each group could be a tenant [2]. Would love to hear more about the use case. I ca
157.
by shayonj 2y ago
heya! Thanks for checking it out. Yeah, I believe you should be able to. Are you basically thinking to have multiple rules where if tenant_id=3, send to the db_3, and so on?
158.
Pg_flo – Easily move and transform data between PostgreSQL databases(github.com)
3 points by shayonj 2y ago|6 comments
159.
by shayonj 2y ago
I have always wondered if anyone used it in a "real life scenario". This was hilarious, thanks for sharing :D
160.
Shrinking Big PostgreSQL Tables with the Copy-Swap-Drop Technique(andyatkinson.com)
5 points by shayonj 2y ago|0 comments
161.
A simple tool to observe PostgreSQL database locks in Rails apps(github.com)
1 points by shayonj 2y ago|0 comments
162.
by shayonj 2y ago
I really like Sequel and use it as well in non rails apps. Its powering pg-osc and pg_easy_replicate for me. Thanks for the project!
163.
by shayonj 2y ago
This had been on my todo list for a while now. It’s like the perfect match between event triggers and logical replication. Would love to hear any feedback and/or other ideas folks have tried in this space.
164.
Beyond logical replication: pg_easy_replicate Supports Tracking DDL Changes(shayon.dev)
22 points by shayonj 2y ago|2 comments
165.
by shayonj 2y ago
Very cool case of using s3 conditional writes for distributed leasing
166.
by shayonj 2y ago
Ankane single handedly is contributing so much back to the industry, in so many ways. Wild!
167.
by shayonj 2y ago
exactly - i missed to talk about this in the post. I think using IF NOT EXISTS can be a sign of a higher degree issue as well. Being more mindful can help.
168.
by shayonj 2y ago
Reindex starts fresh on a temp index and then does a swap in the end - https://www.postgresql.org/docs/current/sql-reindex.html
169.
by shayonj 2y ago
Yeah, def, good call. I have a job that runs nightly or weekly and performs a concurrent reindex on tables, which nicely covers cases like this. Given that lock timeouts are very much "rescuable," I'm also thinking about addr
170.
by shayonj 2y ago
Hey Andrew! It's great to see you here. I agree with everything you said, 100%. I'm honestly torn because I was the first one to recommend `if_not_exists` to engineers, but now I'm reconsidering because this can lead to very
171.
by shayonj 2y ago
I went looking in the postgres code and took it more as a "Feature request" where if the index building / table scanning, etc is interrupted for concurrent builds, PG could drop the index in the end. I can see how PG keeps it
172.
Don't rely on IF NOT EXISTS for concurrent index creation in PostgreSQL(shayon.dev)
90 points by shayonj 2y ago|54 comments
173.
by shayonj 2y ago
Very cool! Thanks for sharing. I am hacking on something similar too and I think there are a lot of interesting use cases to unlock with this model
174.
A tale of using chaos engineering at scale to keep our systems resilient(tines.com)
5 points by shayonj 2y ago|0 comments
175.
Thankful for incidents: embracing chaos to find clarity(tines.com)
3 points by shayonj 2y ago|0 comments
176.
Tech Industry's Moral Vacuum(shayon.dev)
8 points by shayonj 2y ago|2 comments
177.
Use pg_easy_replicate to setup up Logical Replication in PostgreSQL with ease(shayon.dev)
1 points by shayonj 2y ago|0 comments
178.
Is MySQL this slow? Is this visible in production workloads?(twitter.com)
7 points by shayonj 2y ago|0 comments
179.
by shayonj 2y ago
cool project! nice
180.
Fast, Simple and Metered Concurrency in Ruby with Concurrent:Semaphore(shayon.dev)
2 points by shayonj 2y ago|0 comments

More ›