Hacker News new | past | comments | ask | show | jobs | submit | more akane's comments login

That's correct. It allows us to manage the database size over time for tables where we can archive data after a specific period.


We currently use Amazon RDS, which doesn't support custom extensions, so pg_partman wasn’t an option for us. I haven't used pg_partman myself, but it looks to have different features.

I think an external tool is a bit friendlier for people who aren't super comfortable with installing Postgres extensions. Also, it doesn't require a restart.

I'm optimistic that Postgres will make all of this trivial at some point.

Edit: changed "more features" to "different features". One of the main goals is the ability to partition existing production tables without downtime, which seems different than pg_partman.


> I'm optimistic that Postgres will make all of this trivial at some point.

There's considerable ongoing work towards that. If you're interested in helping out, consider testing and reviewing the patchset. That doesn't necessarily require a lot of postgres internals knowledge, user interface feedback after trying is very welcome.



Looks right, yes.


We've been using the tool for around 5 months, but the same approach/triggers for over a year. I wasn't aware the IF/ELSIF trigger approach had potential advantages over EXECUTE, but will definitely look into it.


Yes, we do at Instacart.


Could you speak a bit of the use cases you've found this to be a better tool than competing alternatives, whatever they may be, if you're able to?


We didn't really find anything that fit our needs. We wanted a tool that was simple to use with the ability to do time-based partitioning of existing production tables without downtime.


Assuming the Julia implementation is correct, you could write tests based on output from that.


Currently, a visit record is created as soon as a user lands on a page with the Javascript, but I'm curious to see other ways people want to it.


Unless you have hundreds of unique visitors per second, this shouldn't be a problem.


It's been on Github for a bit, but this is the first big release.


Training searches from conversions (self-improving searches) is kinda interesting. Elasticsearch is an amazing product but it can be hard to configure, especially for beginners.

Edit: spelling


We looked into PostgreSQL search for a bit, but didn't see a way to train search results from past conversions. Does anyone know if this is possible?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: