rkaveland

Joined 2 years ago

Karma

193

Submissions

19

Member since

Mar 26

View on Hacker News

Recent submissions

Comment · 1 year ago

Author here. I will be trying out Kagi for some time. Search is worth paying money for. Thanks for the heads-up!

The librarian immediately attempts to sell you a vuvuzela kaveland.no

478 rkaveland 1 year ago 341 comments

What if that isn't a bool? kaveland.no

1 rkaveland 1 year ago 0 comments

Why avoid where id in with variable number of bind parameters on Postgres kaveland.no

7 rkaveland 2 years ago 0 comments

Batch operations using composite keys in Postgres over JDBC kaveland.no

1 rkaveland 2 years ago 0 comments

Comment · 2 years ago

Author of the blog post here -- that looks like exactly what I needed, so I'm probably going to add a dependency to it to https://github.com/kaaveland/eugene/ so I can delete a ton of code. :-)

That looks fantastic, so I'm actually just going to put a link to it in the post so that more people see it.

Show HN: Eugene helps you write zero downtime schema migrations kaveland.no

1 rkaveland 2 years ago 0 comments

Comment · 2 years ago

A while back, I wrote a blog post that experimented with doing transactional DDL in postgres, and investigating the state of `pg_locks` to check if statements were likely to interfere with queries. I've expanded on this idea and made a tool, that I named `eugene` for the title of the first blog post.

Check out the examples in https://github.com/kaaveland/eugene/tree/main or read the blog post -- I would love to have more ideas for where to take this, both concrete migration hints that `eugene` could show people, but also functionality and ways to integrate it into CI.

Eugene is a CLI tool for reviewing Postgres SQL migration scripts kaveland.no

8 rkaveland 2 years ago 2 comments

Comment · 2 years ago

This is super cool, I love how it suggests safer ways to achieve the same goal for many common risky migrations. Definitely going to sit down and study these.

Comment · 2 years ago

Thanks, I will fix this part. As far as I can tell, it is only the example of what can cause the table rewrite that's wrong, so it would be correct if the example was to make a varchar shorter? Although I guess that's not a table rewrite, only a long validation...