Viewing profile — chanks
chanks
HN member- Joined
- Tue, Jun 22, 2010, 8:33 PM UTC
- HN karma
- 2,008
- Public activity
- 71 items
- HN profile
- View on Hacker News ↗
About chanks
Recent public activity
-
comment
Comment #38800983
You can, but that won't protect you against invalid dates like an actual date type will.
-
comment
Comment #33247020
I'm very curious how well this is working for you in practice, since I've been thinking about what it would look like to share a single Rust UI implementation across a webapp and n…
-
comment
Comment #17221518
And Roda ( https://github.com/jeremyevans/roda ) beats Gin, if you include it: https://www.techempower.com/benchmarks/#section=data-r15&hw=...
- story
-
comment
Comment #14073049
If you have a table that undergoes frequent updates and this is a concern of yours, look into setting a fillfactor on it. This will help Postgres keep writes in the same page, whic…
-
comment
Comment #12575279
Looking at your PR for it ( https://github.com/LuaJIT/LuaJIT/pull/149 ) it sounds as if there are a few issues remaining, but I'm not enough of an expert to know how problematic th…
-
comment
Comment #12407236
A small tree-based router for Ruby apps. https://github.com/jeremyevans/roda
-
comment
Comment #10019970
That is, indeed, what Sequel does. You can query the database object directly (for example, `DB[:posts].where{comments_count > 5}.exclude(poster_name: "Bob").order(:comments_count.…
-
comment
Comment #9580155
Thank you!
-
comment
Comment #9577873
(I'm the author of Que, the job queue discussed in the post most extensively) This isn't terribly surprising to me, since I have an appreciation for what long-running transactions …
-
comment
Comment #8378210
My point is that the only way to wrap your jobs in the same transactions as the rest of your data is to have your job queue in your RDBMS. If you don't have that, you can't guarant…
-
comment
Comment #8377812
It can only be consistent with the rest of your data if the rest of your data is also in Redis.
-
comment
Comment #8377699
The major benefit of putting your queue in your RDBMS, which isn't commonly brought up in these discussions, is that it lets you protect your jobs with the same ACID guarantees as …
-
comment
Comment #7955491
Hi, I'm the author of Que. It's true that you can't really completely solve the idempotence problem for jobs that write to external web services (unless those web services provide …
-
comment
Comment #7748037
Frontline has an excellent episode on the Norfolk Four, a similar case that happened in Virginia: http://www.pbs.org/wgbh/pages/frontline/the-confessions/
-
comment
Comment #7267850
You have some valid criticisms of the implementation, though pgsql-hackers has their reasons ( http://www.postgresql.org/message-id/CAHyXU0ybwZZUbuQQVFQMK3... ) for the way things …
-
comment
Comment #7266984
PL/pgSQL function plans are cached. Functions written in other languages may not be, I don't know, but in my experience PL/pgSQL is the most widely used. http://www.postgresql.org/…
- story
-
story
Show HN: Que, a Ruby-PostgreSQL job queue with ~20x the throughput of DelayedJob
Hi everyone - I wrote a job queue called Que, which uses Postgres' advisory locks to manage jobs very efficiently. My goal is to make it easy to cover jobs with the same ACID guara…
- story
-
comment
Comment #6763037
I'm really interested in suggestions or comments about Que - I'm trying to make it as durable as possible while retaining its speed. I'm also looking for a steady job using Ruby, i…
- story
- story
-
comment
Comment #5701015
What I would find helpful is some sort of operator to merge two JSON values. I use a JSON field to collect various statistics relating to a table's rows, and it'd be nice to not ha…
- story