Live data from Hacker News

Postgres.app

postgresapp.com

21–30 of 158 posts

Re: Postgres.app

#21

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 have been using it for 2 yesrs now. Did not have any problem upgrading changing the version etc. Homebrew breaks things often. The App just works I never have to care about it.

Re: Postgres.app

#22
post #6

It looks nice for beginners but personally I find that a simple docker-compose file per project that spins up a postgresql container works pretty nicely and is really easy to use. I just run `docker-compose up -d` and I have a database running. Docker containers also stay out of the way of the os and I can run the right versions for whichever project.

I think you and this app are solving quite different problems. For you (and most people replying) it sounds like PostgreSQL is a component in a larger app that will eventually get deployed and run somewhere else and only be interacted with via that app.

Others (like myself) use PostgreSQL as a local datastore and analysis engine. All my interaction with the database is via ad hoc SQL commands and locally run scripts and desktop applications. For this usecase, something like this is much easier to use than docker compose.

Re: Postgres.app

#26
post #22
post #6

It looks nice for beginners but personally I find that a simple docker-compose file per project that spins up a postgresql container works pretty nicely and is really easy to use. I just run `docker-compose up -d` and I have a database running. Docker containers also stay out of the way of the os and I can run the right versions for whichever project.

I think you and this app are solving quite different problems. For you (and most people replying) it sounds like PostgreSQL is a component in a larger app that will eventually get deployed and run somewhere else and only be interacted with via that app. Others (like myself) use PostgreSQL as a local datastore and analysis engine. All my interaction with the database is via ad hoc SQL commands and locally run scripts…

What’s your use case? (Whatever you’re comfortable sharing.)

Re: Postgres.app

#27
Had never heard of plv8. Has anyone used it for anything at scale? Quite cool with JS directly in functions although the dynamic typing could be a bit strange …

Re: Postgres.app

#29
post #20

Earlier quoted context omitted.

Postgres.app supports multiple versions, and doesn't put random files in /etc/foo - everything is in the right place for a Mac app, i.e. Postgres itself is in /Applications and the database is in ~/Library/Application\ Support/Postgres.

That's interesting, but my situation is that I'm developing on macOS and deploying on a linux box so my postgres setup with docker can look virtually identical.

Why worry about one more level of abstraction, if using the same version of Postgres should be enough?

Re: Postgres.app

#30
post #20

Earlier quoted context omitted.

That's interesting, but my situation is that I'm developing on macOS and deploying on a linux box so my postgres setup with docker can look virtually identical.

Why worry about one more level of abstraction, if using the same version of Postgres should be enough?

> if using the same version of Postgres should be enough
Post reply on HN