Postgresapp: Should Postgres.app 2.2 be available now from "Check for Updates"?

Created on 26 Oct 2018  Â·  4Comments  Â·  Source: PostgresApp/PostgresApp

I just did the update, but I got 2.1.5 instead of 2.2

Most helpful comment

@edbond In that case, you should do the following:

1) Make sure the old version of Postgres.app is runninng
2) Create a dump of your PG 10 database using pg_dumpall (see https://postgresapp.com/documentation/migrating-data.html and https://www.postgresql.org/docs/current/static/app-pg-dumpall.html)
3) Quit Postgres.app and install the new version
4) Create a new server with version 11
5) Restore your previously generated dump file

All 4 comments

Previously Postgres.app always downloaded the latest version including new major versions. That was convenient, but had the downside that the app kept getting bigger and bigger (eg. you download Postgres.app with 9.5 and 9.6, then it updates and include PostgreSQL 9.5, 9.6, and 10, this year we would have 9.5, 9.6, 10, and 11...)

At some point the app gets so big that it is a problem (eg. the latest version with all the binaries has an uncompressed size of 870MB!)

So I changed it that the automatic update only installs minor updates. If you want the next major version of PostgreSQL, you need to download it manually.

It's a bit confusing, but I'm not sure how else we can do that? I want to have easy updates, but lots of people have limited disk space and / or slow internet speeds, so we can't keep growing Postgres.app. And throwing out old versions in automatic update also isn't a good idea, because then we'd break installations of people using them...

Hi,

I don't see any problems with that, as long as maybe the update dialog
could be modified to include a message that basically says as much as
you've indicated here. Something along the lines of, "Hey, if you want the
latest version that includes version X of postgres, you'll need to download
rather than update".

Thanks for the reply and the great app!

On Mon, Oct 29, 2018 at 6:57 AM Jakob Egger notifications@github.com
wrote:

Previously Postgres.app always downloaded the latest version including new
major versions. That was convenient, but had the downside that the app kept
getting bigger and bigger (eg. you download Postgres.app with 9.5 and 9.6,
then it updates and include PostgreSQL 9.5, 9.6, and 10, this year we would
have 9.5, 9.6, 10, and 11...)

At some point the app gets so big that it is a problem (eg. the latest
version with all the binaries has an uncompressed size of 870MB!)

So I changed it that the automatic update only installs minor updates. If
you want the next major version of PostgreSQL, you need to download it
manually.

It's a bit confusing, but I'm not sure how else we can do that? I want to
have easy updates, but lots of people have limited disk space and / or slow
internet speeds, so we can't keep growing Postgres.app. And throwing out
old versions in automatic update also isn't a good idea, because then we'd
break installations of people using them...

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PostgresApp/PostgresApp/issues/475#issuecomment-433868446,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYgWKU411rKsK6yqUET_K_7MgSYJThcxks5upt8EgaJpZM4X8fj3
.

--

Chris Marx
Senior Software Engineer
ZevRoss - Know Your Data
Data Science & Spatial Analysis
209 N. Aurora St, 2nd Floor
Ithaca, NY 14850
www.zevross.com

What is the upgrade path now?
I have a 9.5, 9.6, 10 version (use version 10 only). Want to download 11 and migrate data.
How to do that correctly? Maybe it needs to be described in readme.
Thanks!

@edbond In that case, you should do the following:

1) Make sure the old version of Postgres.app is runninng
2) Create a dump of your PG 10 database using pg_dumpall (see https://postgresapp.com/documentation/migrating-data.html and https://www.postgresql.org/docs/current/static/app-pg-dumpall.html)
3) Quit Postgres.app and install the new version
4) Create a new server with version 11
5) Restore your previously generated dump file

Was this page helpful?
0 / 5 - 0 ratings