51–60 of 254 posts
Earlier quoted context omitted.
I think many mercurial users would disagree with you about git.
Are we talking about market dominance, mind share or the idea that there's no real competition? MySQL and Oracle exist. Mercurial and perforce exist. I'm not sure it's a terrible stretch to compare git and postures.
Seems zheap didn't make it this time either?
- 12-10-2020: "Most regression tests are passing, but write-speeds are still low."
Tangential to this topic: If I have a Django + PG query that takes 1 second and I want to deeply inspect the breakdown of that entire second, where might I begin reading to learn what tools to use and how?
EXPLAIN (ANALYZE, BUFFERS) Take the result of this and paste it into https://explain.depesz.com/ which will make it human readable. Understanding this is sometimes very easy, but if you want to understand what they _really_ mean, you can read depesz.com
Earlier quoted context omitted.
> Java for enterprise server software. Big corporations are horribly inefficient and Enterprise Software necessarily so from that...if you're saying Java is terrible by nature of it being the goto for enterprise, then that makes sense. It took 20 years for it to swap places with COBOL and I expect it will be something else in 20 more.
I don't work with Java, but I can think of a few advantages off the top of my head: - appreciation of backwards-compatibility (here it wins with Python); - great debuggers and performance tools (e.g. Java Flight Recorder or Eclipse Memory Analyzer); - easy deployment - you can just give someone a fat JAR (here it wins with all scripting languages, so Python, Ruby, PHP, or any other flavour of the month); - industry-g…
After using Python, Go, PHP, and C++ it's easy to see why Java is the go-to language for server development.
I'm thinking of using Postgres for a project, but a DBA friend told me operationally it's more challenging than MySQL. Unfortunately, he can't elaborate. Does anyone have real work experience? Or is it based on outdated "PG must manually vacuum frequently"?
Your DBA friend is stuck in 2000's. Let dinosaurs die and you go with PGSQL because is superior to MySQL on everything. And don't take my word for it, see for yourself here: https://en.wikipedia.org/wiki/Comparison_of_relational_datab... And MySQL is an Oracle product these days, go with MariaDB instead as this one is a MySQL fork made by the original papa of MySQL.
Are we still going to need PgBouncer when there are a large number of connections?
Earlier quoted context omitted.
No DDL transactions, no materialized views, the list is endless. There's almost no reason to pick MySQL for a new project.
MySQL and mariadb have first class temporal tables. Pg has compile requirement and so cannot use in AWS RDS.
There’s a pl/pgsql reimplementation of temporal tables specifically for that use case.
Earlier quoted context omitted.
Are we talking about market dominance, mind share or the idea that there's no real competition? MySQL and Oracle exist. Mercurial and perforce exist. I'm not sure it's a terrible stretch to compare git and postures.
I think the point is that git isn't "so much better" than mercurial, while pgsql has had a lead on mysql for quite some time on a lot of technical measurements.