Live data from Hacker News

Postgres.app

postgresapp.com

41–50 of 158 posts

Re: Postgres.app

#41
post #37

I've happily used that on OSX (simpler than docker etc.), now I've switched to Windows, anything like that for Windows?

Obviously not a GUI, but WSL is pretty nice for this, even if you don't need it for anything else. You can run things like wsl.exe -d Ubuntu -u root /some/linux/script From powershell or the cmd.exe console. There's a bit of fiddling required to connect from windows to the WSL postgres instance, but once that's done, it's a nice setup. Edit: You can also use WSL as a sort of "docker like" setup, using wsl --export /…

Yes, this is what I'm currently doing (or using WSL directly together with Clion)

Re: Postgres.app

#42
post #32

Earlier quoted context omitted.

Docker on Mac is a performance and battery hog in my experience.

It also keeps yammering on and on about new versions and required updates. Just that is reason enough to get rid of it.

"Oh no, I have to update my software!"

Are you serious?

Re: Postgres.app

#44
Been a Postgres.app user for years, it's been great. There are other more "sophisticated" setups that have advantages (and disadvantages!) but nothing beats the convenience, in my eyes, of Postgres.app.

Re: Postgres.app

#45

Earlier quoted context omitted.

> beginners Why is this for beginners? Because it is so easy to use? I guess I am a beginner then. > works pretty nicely Postgres.app works perfectly and is very minimal in system requirements vs having docker running and the amount of storage it requires.

How good is the upgrade story? That's typically the achilles heel of GUI installers (vs. installing using homebrew).

I've had the exact opposite experience with Homebrew vs GUI installers. Postgres.app has never had any issues, while Homebrew postgres breaks every time I run `brew update`, because of the way homebrew handles icu4 library dependencies.

Re: Postgres.app

#46

I've always preferred Docker for setting up databases and database-like services on a development machine because then everything is nicely isolated. i.e no need to worry about random files in /etc/foo, easy to setup many versions per project etc. This is what I've been using for Postgres: docker volume create postgres docker run -d \ -p 127.0.0.1:5432:5432 \ -v postgres:/var/lib/postgresql/data \ --name postgres \ -…

I love using Docker Compose in theory, but I've found it really difficult to do local development with a "Docker only" setup on Mac, due to the performance issues with the filesystem layer (even when using cached volumes, etc). Ruby gemfiles and node_modules are big culprits here, since they involve a lot of filesystem accesses to load/install dependencies. It might be more manageable if I was just using Postgres from docker and had e.g. rubyenv and nodenv installed locally, but that sacrifices a lot of the benefits you gain from having a docker-compose setup, and I've never had any problems with managing multiple PG versions in my Postgres.app install.

Re: Postgres.app

#47
post #39

Why use postgre instead of sqlite?

Off the top of my head:

Postgres is a client-server system, with full user access controls and multiple client connections.

Postgres has PostGIS (geographic data) and foreign data wrappers.

Postgres is more scalable than Sqlite and can work with larger datasets over multiple instances.

Re: Postgres.app

#48

I've always preferred Docker for setting up databases and database-like services on a development machine because then everything is nicely isolated. i.e no need to worry about random files in /etc/foo, easy to setup many versions per project etc. This is what I've been using for Postgres: docker volume create postgres docker run -d \ -p 127.0.0.1:5432:5432 \ -v postgres:/var/lib/postgresql/data \ --name postgres \ -…

> because then everything is nicely isolated

This is why we use SQLite for all the things. I don't even remember what a database installation process looks like anymore. It's just a nuget dependency and some code for us.

Re: Postgres.app

#49
post #38

Earlier quoted context omitted.

I set up postgres.app for my wife, who's a PM. She used it to crunch data that was too big for Excel, her previous tool of choice.

I'm curious, why postgres.app and not SQLite? I'd usually reach for SQLite as my next step up from Excel, but maybe that's wrong (it's very possible that you're talking about an order of magnitude more data than I am).

Don’t know why you’re being downvoted, SQLite is a perfect companion for local adhoc data analysis, up to a few GB of data. It is even supported by OSS BI tools like Metabase, so its a no brainer compared to a full blown PG!

Re: Postgres.app

#50
post #35

For a really nice client for macOS see Postico: https://eggerapps.at/postico/ (not affiliated, just a fan)

It's mentioned and linked in the article. And "[i]t’s made by the same people that maintain Postgres.app."
Post reply on HN