Live data from Hacker News

PostgreSQL 14

postgresql.org

271–280 of 293 posts

Re: PostgreSQL 14

#271
post #16

If you’d like to try out PostgreSQL in a nice friendly hosted fashion then I highly recommend supabase.io I came from MySQL and so I’m still just excited about the basic stuff like authentication and policies, but I really like how they’ve also integrated storage with the same permissions and auth too. It’s also open source so if you can to just host it yourself you stil can. And did I mention they’ll do your auth fo…

Would you mind expanding on what's so appealing about Supabase (i.e. Firebase). I feel like I live in a cave because I haven't quite understood what problem Supabase/Firebase is solving for.

All those reasons + not owned by google.

I prefer to use companies where you're using their bread and butter service. That way you know they won't suddenly lose interest in it, which google has a reputation for, especially anything to do with google cloud.

I just find what Supabase it trying to do matches up exactly with what I wanted - it solves 90% of my developer headaches and all works together nicely.

Plus I just get good vibes from Supabase in general.

Re: PostgreSQL 14

#272

Earlier quoted context omitted.

pgAdmin 4 has made rapid strides. If you haven't checked it out recently (~6 mos?) you may be pleasantly surprised. Many of the rough edges have been sanded off.

Interesting, it’s been roughly that amount of time since I’ve last used it. I might check it out again.

It's still not the most polished thing in the world, but few IDE-ish tools are... particularly free ones.

I've used a lot of very very expensive ones that aren't as polished as pgAdmin4.

The whole "native app with a web interface" thing is... probably not anybody's idea of "ideal," but I 100% respect it. It's free and it's multiplatform. Choices and compromises were made to achieve that and I don't know that I would have done differently when faced with the same constraints.

Re: PostgreSQL 14

#273

Earlier quoted context omitted.

I stick to standard SQL syntax/features whenever possible as well, but... Honest question: how often do you switch databases? I've never really found myself wanting or needing to do this. Only time I could really see myself wanting to do this is if I was writing some kind of commercial software (eg, a database IDE like DataGrip) that needed to simultaneously support various multiple databases. > MySQL It feels partic…

We got an application which has been developed for over 20 years with the mentality of "we're never switching db's". Yet now we are, because some core customers demand MSSQL support... Of course the db we're using supports all kind of non-standard goodness that has been exploited all over. Gonna be fun times ahead...

Yikes. Good luck with that.

(I don't mean that sarcastically. I truly wish you luck.)

Re: PostgreSQL 14

#274

Earlier quoted context omitted.

I guess I’m still getting used to it, but it always takes a few extra steps to open things like views and functions, autocomplete needs configuring to work properly, and a couple of other features I’m blanking on at the moment. It’s all small stuff, but it can add up.

Yes, they are in separate folders, but don't think it has to do with PG per se. My autocomplete works well, don't think I did anything special. Maybe added a schema to the "search path?" May have been pgcli (which I also recommend).

Yeah, ultimately it’s the best alternative I’ve used so far, and it also supports other languages, so I’m likely to continue using it.

Re: PostgreSQL 14

#275
post #263

Earlier quoted context omitted.

I used pgsanity at the CLI for a while when I unfortunately had coding and testing split between two machines. Can be used with any editor. https://github.com/markdrago/pgsanity

Interesting, thanks! I wonder how easy it would be to write a VS Code plug-in using that.

If you can run a linter, you can run it as well.

Re: PostgreSQL 14

#276

Earlier quoted context omitted.

Yes, and most of these love/hate memes are blowned out of proportion by people who don't actually have any real expertise in those technologies, but just parrot whatever they've read in some memes.

You're exactly correct. Tons of "XYZ is bad" because of some meme that they don't even understand or have context on that hasn't been relevant for years. I have no idea if MongoDB is good or bad at this point, but the comments of "haha it's mongo" are completely devoid of meaningful content and should be flagged.

Because it's (or at least it definitely WAS) true.

There are valid use-cases for mongo but for vast majority of things, you're better to start with postgres. And I say that as an early adopter - I really wanted mongo to succeed but it just failed all of my expectations. All of them.

BTW: this is post about postgres.

Re: PostgreSQL 14

#277
post #209

Earlier quoted context omitted.

>Sorry, I didn't mean offense. Don't be a SJP, you have the right to offend someone when he talks bs.

What does SJP mean?

"Social Justice" something, probably, like in "SJW" = "Social Justice Warrior".

Some people see politeness or compassion as weakness, and ttherefore use terms acknowledging it as pejoratives. The funny thing is, they think this makes objects of derision of their targets, and don't realise that it's themselves it does so.

Re: PostgreSQL 14

#278

Earlier quoted context omitted.

As someone that mostly shared that opinion for the last decade or more, I recently set up a cluster for work, and everything seems much more production level quality than I remember or what I assumed it was going to be like. I'm not the one using it for queries every day, but I did do a bunch of testing for replication and failed nodes to confirm that I understood (and could rely) on the claims of robustness, and it…

One thing that turned me away from MongoDB was their utter lack of care for your data integrity that they displayed for years. Some of those instances were even documented. Then there were some bad defaults - some could _also_ cause data loss. For any component that's viewed as a database (as opposed to, say, cache), data integrity is one of the most important metrics (if not THE most). In contrast, PostgreSQL data l…

Although MongoDB claims in an undated article entitled "MongoDB and Jepsen"[65] that their database passed Distributed Systems Safety Research company Jepsen's tests, which it called “the industry’s toughest data safety, correctness, and consistency Tests”, Jepsen published an article in May 2020 stating that MongoDB 3.6.4 had in fact failed their tests, and that the newer MongoDB 4.2.6 has more problems including “retrocausal transactions” where a transaction reverses order so that a read can see the result of a future write.[66][67] Jepsen noted in their report that MongoDB omitted any mention of these findings on MongoDB's "MongoDB and Jepsen" page.

from https://en.wikipedia.org/wiki/MongoDB#Bug_reports_and_critic...

Re: PostgreSQL 14

#279

Earlier quoted context omitted.

As someone that mostly shared that opinion for the last decade or more, I recently set up a cluster for work, and everything seems much more production level quality than I remember or what I assumed it was going to be like. I'm not the one using it for queries every day, but I did do a bunch of testing for replication and failed nodes to confirm that I understood (and could rely) on the claims of robustness, and it…

Jepsen test suite completely tore them a new one. I don't trust any allegedly distributed database that gets excoriated that badly by Aphyr. https://jepsen.io/analyses/mongodb-4.2.6 That's just a bit more than a year ago. Come on. MongoDB is like Mysqldb. I am so so so tired of hearing "that's been fixed, it's great now", doing a paper-thin dive into things, and seeing there are massive problems still. I used MongoDB…

Even worse, MongoDB lied about having fixed these bugs.

https://en.wikipedia.org/wiki/MongoDB#Bug_reports_and_critic...

Post reply on HN