ahachete

28 ms·

241.
by ahachete 7y ago
Or Patroni ( https://github.com/zalando/patroni ), a better option. But it is complex to setup, requires other external tools too (DNS, virtual IPs, Envoy proxy, etc) and none of that is included in Postgres. Postgres HA
242.
by ahachete 7y ago
> You do need to understand your access patterns well, and develop migration plans when they change. This sounds like a minor issue, but it's a huge operational pain. Migrating a data structure to accommodate new queries involves op
243.
by ahachete 7y ago
Here is the code for the queries: https://gitlab.com/ahachete/pgmongojoins/-/tree/master/post-... Feel free to send a MR improving it.
244.
by ahachete 7y ago
Co-author here. Thank you all for your comments. While I understand is tempting to easily conclude that this is apples-to-oranges or that "obviously a relational database is better at data relationships", I recommend to dive deepe
245.
Comparison of Joins: MongoDB vs. PostgreSQL(enterprisedb.com)
62 points by ahachete 7y ago|68 comments
246.
JOINs the hard way: comparing MongoDB and Postgres(ongres.com)
18 points by ahachete 7y ago|1 comments
247.
by ahachete 7y ago
Few production clusters have checksums turned on. Since they cannot be turned online, only clusters of newer project turn it on --and even then, they are still unknown to many. So we cannot rely on this, and WAL stream corruption is a notab
248.
Comparison of Joins: MongoDB vs. PostgreSQL(enterprisedb.com)
1 points by ahachete 7y ago|0 comments
249.
by ahachete 7y ago
How does it work in the event of real time changes happening on the database(s)? It appears not to use logical decoding/replication. If so, how it does sync the data? It sounds like a hard problem, and not very efficient, to do it with
250.
How AWS’s Firecracker virtual machines work(amazon.science)
2 points by ahachete 7y ago|0 comments
251.
by ahachete 7y ago
Ideally, you would be absolutely right and I would not disagree with you. But I strongly do, based on many years of experience in the field. Out of all the customers we help with their Postgres infrastructure, and that includes several $B c
252.
by ahachete 7y ago
> I find this hard to believe. Maybe on the very rare occasion where the problem is tied to production and irreproducible elsewhere, but my experience has been that most troubleshooting happens on development, testing, staging, etc serve
253.
by ahachete 7y ago
I've used Joe quite a bit, and all I can say is that it's a great idea that solves a noticeable problem: troubleshoot your queries. It may not look like is a hard challenge: but the reality is that most troubleshoot them in produc
254.
GSMA has cancelled MWC Barcelona 2020(gsma.com)
21 points by ahachete 7y ago|2 comments
255.
by ahachete 7y ago
I know well. I have read most CCDB posts and architecture documentation. Pretty good job. There are several ways to map a row to K-V stores, and different databases have chosen different approaches, I'm not referring specifically to CC
256.
by ahachete 7y ago
Don't get me wrong, both RocksDB and the work done by CCDB is pretty cool. Yet I still believe that layering a row model as the V of a K-V introduces by definition inefficiencies when accessing columnar data in a way that row stores do
257.
by ahachete 7y ago
> Right tool for the right job. Users in Tokyo won't be editing accounts for users in Austrailia. There's often a natural partition [...] Exactly. That's why I'd say for tools that support multi-master to provide and
258.
by ahachete 7y ago
I don't agree with the "fine" in the "fine first approximation". I believe it is indeed a bad solution. LWW/LUW basically leads to data loss. Something unexpected for Postgres users. Which potentially undermine
259.
by ahachete 7y ago
I'm not a big fan of conflict resolution, and LWW is a pretty bad choice in most cases. Conflict resolution means data loss (it violates the D of ACID, as an user expects that a transaction that was committed would endure, but it is de
260.
by ahachete 7y ago
As I mentioned upthread ( https://news.ycombinator.com/item?id=22224019 ) and in the other thread ( https://news.ycombinator.com/item?id=22140773 ), it's not that easy. And simple rules to compute paramete
261.
by ahachete 7y ago
That's the next step we will be taking: offering subsets of parameters that are recommended to be tuned, depending on the "desired" level of expertise. And then, some more direct indications on how to tune this parameters for
262.
by ahachete 7y ago
It's custom made.
263.
by ahachete 7y ago
If it would be this straightforward, why doesn't Postgres do this directly? There is the misconception that tuning Postgres is just about the memory and CPUs. It's also a lot about the usage patterns, whether you use or not a conn
264.
by ahachete 7y ago
Thanks for all the feedback. We will definitely take this into account for future reviews of the UI.
265.
by ahachete 7y ago
As of today, it is more of a Reference than a Guide. This is intended. Further enhancements of the website will include functionality to fully help less and more experienced users to fine tune PostgreSQL configurations. Read more from a rec
266.
by ahachete 7y ago
Absolutely. But we found over many years that know which 5-10 (out of the 300) and what values are good is a hard job for most. Despite that, we end up tuning 30-40 for most of the customer environments we work with. For instance, logging (
267.
by ahachete 7y ago
Maybe I haven't blogged (yet!) about that, but definitely spoken about it: https://aht.es/#talks-postgresql_configuration_for_humans
268.
by ahachete 7y ago
We will check both, thanks!
269.
by ahachete 7y ago
Noted. Good idea ;)
270.
by ahachete 7y ago
Yes, we did it ourselves from scratch. Thank you!

More ›