4 ms·

Yeah, if you are running Postgres natively on OSX instead of in Docker you are behind the times. I’m sure this will be downvoted, but it needs to be said.

Doctor_Fegg 6y ago
No it doesn’t. There are several Mac-native apps, such as QGIS, for which Postgres is a sensible local datastore. Running it in a container for this is an entirely unnecessary complication.
jdboyd 6y ago
How does permeance compare? Also that doesn't look like a good option for M1 mac users.
slezyr 6y ago
> you are behind the times Seriously? What is wrong with running programs natively without any layers in between? Also, IIRC PostgreSQL isn't recommended to be run in docker due to a possible data loss?
- user-the-name 6y ago
  Because your average Unix program will basically spread itself all over your system, and is nearly impossible to remove. I don't want to pollute all my system directories with random gunk. Keeping things in containers keeps it from making a mess, and that alone makes it worth it, to say nothing about the advantages for handling dependencies or running multiple copies or versions.
  - Doctor_Fegg 6y ago
    The original issue is about Postgres.app which very deliberately _doesn’t_ spread itself all over your system.
  - cat199 6y ago
    your average unix program, esp. something like postgres which has been developed for literally decades, will basically spread itself into well defined compile-time locations which are easily removed by any competent package manager or even competent manual build (touch package.stamp && make install && find $prefix -cnewer -type f package.stamp > package.file-list ) It's only 'random' if you don't know what you are doing. Containers are fine and often good, but their existence/availability doesn't 'supercede' real knowledge.
cat199 6y ago
... alternately, if you think running in docker is suitable for and solves all problems, you are a noob.

Doctor_Fegg 6y ago

No it doesn’t. There are several Mac-native apps, such as QGIS, for which Postgres is a sensible local datastore. Running it in a container for this is an entirely unnecessary complication.

jdboyd 6y ago

How does permeance compare? Also that doesn't look like a good option for M1 mac users.

slezyr 6y ago

> you are behind the times Seriously? What is wrong with running programs natively without any layers in between? Also, IIRC PostgreSQL isn't recommended to be run in docker due to a possible data loss?

user-the-name 6y ago
Because your average Unix program will basically spread itself all over your system, and is nearly impossible to remove. I don't want to pollute all my system directories with random gunk. Keeping things in containers keeps it from making a mess, and that alone makes it worth it, to say nothing about the advantages for handling dependencies or running multiple copies or versions.
- Doctor_Fegg 6y ago
  The original issue is about Postgres.app which very deliberately _doesn’t_ spread itself all over your system.
- cat199 6y ago
  your average unix program, esp. something like postgres which has been developed for literally decades, will basically spread itself into well defined compile-time locations which are easily removed by any competent package manager or even competent manual build (touch package.stamp && make install && find $prefix -cnewer -type f package.stamp > package.file-list ) It's only 'random' if you don't know what you are doing. Containers are fine and often good, but their existence/availability doesn't 'supercede' real knowledge.

cat199 6y ago

... alternately, if you think running in docker is suitable for and solves all problems, you are a noob.