JelteF

7 ms·

31.
by JelteF 3y ago
Zeekraal is really nice in lots of dishes. It goes well with at least pasta, patatoes and salads.
32.
by JelteF 3y ago
PgBouncer maintainer here, so obviously biased. But I think currently PgBouncer should still be the default connection pooler that you choose. There's a few newer options: Odyssey, pgcat, and supavisor. But all focus on a solving 1 or
33.
PgBouncer 1.21.0 released with prepared statement support(pgbouncer.org)
20 points by JelteF 3y ago|3 comments
34.
PgBouncer 1.21.0 – "The one with prepared statements"(github.com)
2 points by JelteF 3y ago|0 comments
35.
by JelteF 3y ago
Yeah, okay of course you can take it to far. But in the general case I would not want to discourage people from opening "trivial" PRs. Since those are the PRs that cost me the least time to manage, while still improving the projec
36.
by JelteF 3y ago
Personally as an open source maintainer I like the typo/wording fixes/automated refactor PRs the most. There's almost no effort needed from my side to review them, so I almost always merge those very quickly. It's the PR
37.
by JelteF 3y ago
These are the two relevant patches that I know of (there might be more): 1. https://github.com/postgres/postgres/commit/3838fa269c15706d... 2. https://github.com/postgres/postgres/co
38.
by JelteF 3y ago
Pgbouncer maintainer here. Overall I think this is a great description of the tradeoffs that PgBouncer brings and how to work around/manage them. I'm actively working on fixing quite a few of the issues in this blog though 1. Name
39.
Citus supports the PostgreSQL MERGE command, as of Citus 12.0(citusdata.com)
2 points by JelteF 3y ago|0 comments
40.
Rush Hour Sudoku Puzzle(yusitnikov.github.io)
2 points by JelteF 3y ago|0 comments
41.
by JelteF 4y ago
There's many uses for random numbers where cryptographic random is unnecessary, but where different runs of the program should use different pseudo random sequences.
42.
by JelteF 4y ago
I agree with the general gist if your post, but still wanted to call out the "git worktree" because that would solve the problem you're describing. It's pretty much a better version of cloning the repo twice.
43.
by JelteF 4y ago
ZZ is only 3 keystrokes as opposed to 4 for :x (shift + z + z = 3 and shift + ; + x + enter = 4). It also doesn't require timing the release of shift before the press of x.
44.
by JelteF 4y ago
Hold shift and press Z twice will also close and save. It's only three key presses instead of 4 for :x (shift + ; + x + enter)
45.
by JelteF 4y ago
Because then people with those allergies won't buy your product. And you want people to buy your product. So if you're sure that the allergens are not in your product, then why would you tell people with those allergies not to buy
46.
by JelteF 4y ago
If you're the sysadmin, then chances are high you can add this to the base image of all the systems you regularly touch.
47.
by JelteF 4y ago
Reading this gave me flashbacks to the time when I tried figuring out why my laptop keyboard was typing letters by itself randomly. Turns out the always-on-usb feature of the laptop was causing some short circuiting: https://foru
48.
by JelteF 4y ago
Honestly these are my favorite PRs to receive for my open source side projects. They are easy to review and approve. The smaller the PR the less time consuming it is for me to deal with them. Big PRs that add complex new features are also a
49.
Distributed Postgres goes full open source with Citus: why, what and how(citusdata.com)
7 points by JelteF 4y ago|0 comments
50.
by JelteF 4y ago
I think simply having an image of what a solved network looks like would help a lot.
51.
by JelteF 4y ago
There's a way around this: Under "branch protection rules" in the settings for the repo, you can require certain "status checks" to be green before merging. This has as an added benefit that it works for allowing &q
52.
by JelteF 4y ago
Making HA easier while self-hosting is definitely something that's high on our list of future improvements. I wouldn't be surprised if there will be some announcements regarding this in the coming year. One of the main issues (imo
53.
by JelteF 4y ago
This is the release announcement with more details on the open sourced things and all the other totally new features: https://www.citusdata.com/blog/2022/06/17/citus-11-goes-full... (sadly the accompanyi
54.
by JelteF 4y ago
I don't think I agree that this is a duplicate of the commit that was submitted yesterday. The release of Citus 11 contains much more, than only the enterprise features that were open sourced. Also this post has a lot more details on w
55.
Citus 11 for Postgres goes fully open source, with query from any node(citusdata.com)
62 points by JelteF 4y ago|3 comments
56.
by JelteF 4y ago
This one surprised all of us on the Citus dev team, when we were reviewing what we were open sourcing. This "feature" was never intended to be Enterprise only and not having it in the open source repo was simply an honest mistake.
57.
by JelteF 4y ago
Yes, pg_dist_authinfo is an easier to use alternative to .pgpass. And no worries about spoiling the announcement a bit. Seeing this on the frontpage of HN made my day!
58.
by JelteF 4y ago
Really nice seeing this commit, that I pushed this morning to Github, on the frontpage of HN a few hours later :) It's awesome that other people are just as excited about open-sourcing as we are. But if you like this definitely keep an
59.
by JelteF 4y ago
The "Annoyances" section of the "Filter lists" tab is where you can enable blocking of cookie banners/popups.
60.
by JelteF 5y ago
We have some users of Citus that are combining it with Postgis (Postgis is a big reason for many people to use Postgres). So it definitely sounds interesting to run this benchmark too. Thanks for sharing a link to the suite, I had not seen

More ›