4 ms·

I love new features in Postgres, but I hate upgrading. Transition, especially for dev environment is always way too complex and not obvious at all. If there is

I love new features in Postgres, but I hate upgrading. Transition, especially for dev environment is always way too complex and not obvious at all. If there is one feature I wish PG had, it is recognizing old format db and offering one command that can in place upgrade damn db, without me googling it every time.

nunwuo 10y ago
> If there is one feature I wish PG had, it is recognizing old format db and offering one command that can in place upgrade damn db, without me googling it every time. So your having to Google for five minutes when doing a major version upgrade is the biggest flaw in modern postgres? Oh come on now. P.S. pg_upgradecluster in Debian would probably do this for you without googling
- jeffdavis 10y ago
  It's not an unreasonable request, and certainly worth some effort to improve. That being said, if upgrade is the biggest problem, that's great news!
- desireco42 10y ago
  Hey, I know it sounds a little spoiled, but when I am focused on something else, especially in development context, I could use some more automated way. I am sorry you got downvoted, but as you can see, it is a genuine pain that software should do for us. On other hand, PG is fantastic DB and it is great I have this as a problem.
rpedela 10y ago
You mean pg_upgrade? http://www.postgresql.org/docs/9.5/static/pgupgrade.html http://www.postgresql.org/docs/9.5/static/pgupgrade.html
- snuxoll 10y ago
  pg_upgrade is a pretty reasonable compromise, but it would be nice if an upgrade didn't require your entire database be taken offline for the duration. I can install a new MS SQL Server instance, attach a database from the old instance and be going in under a minute of downtime - this is literally the only pain point I have with Pq, but considering I don't typically upgrade EVERY release (I still have 9.4 instances that have no reason to be upgraded to 9.5 since the applications aren't in-house) it's not typically a huge deal.
  - oskari 10y ago
    pg_upgrade in link mode typically takes less than a minute to run unless you have a lot of tables; the runtime is dependant on the number of database objects, not rows or size of the database. Database statistics are not preserved across pg_upgrade so you'll have to run ANALYZE on the database after the upgrade which may take a while as it usually needs to read all or almost all of your data. I just recently upgraded a ~1 TB database, the actual upgrade process took less than a minute but analyzing it took much longer.

nunwuo 10y ago

> If there is one feature I wish PG had, it is recognizing old format db and offering one command that can in place upgrade damn db, without me googling it every time. So your having to Google for five minutes when doing a major version upgrade is the biggest flaw in modern postgres? Oh come on now. P.S. pg_upgradecluster in Debian would probably do this for you without googling

jeffdavis 10y ago
It's not an unreasonable request, and certainly worth some effort to improve. That being said, if upgrade is the biggest problem, that's great news!
desireco42 10y ago
Hey, I know it sounds a little spoiled, but when I am focused on something else, especially in development context, I could use some more automated way. I am sorry you got downvoted, but as you can see, it is a genuine pain that software should do for us. On other hand, PG is fantastic DB and it is great I have this as a problem.

rpedela 10y ago

You mean pg_upgrade? http://www.postgresql.org/docs/9.5/static/pgupgrade.html http://www.postgresql.org/docs/9.5/static/pgupgrade.html

snuxoll 10y ago
pg_upgrade is a pretty reasonable compromise, but it would be nice if an upgrade didn't require your entire database be taken offline for the duration. I can install a new MS SQL Server instance, attach a database from the old instance and be going in under a minute of downtime - this is literally the only pain point I have with Pq, but considering I don't typically upgrade EVERY release (I still have 9.4 instances that have no reason to be upgraded to 9.5 since the applications aren't in-house) it's not typically a huge deal.
- oskari 10y ago
  pg_upgrade in link mode typically takes less than a minute to run unless you have a lot of tables; the runtime is dependant on the number of database objects, not rows or size of the database. Database statistics are not preserved across pg_upgrade so you'll have to run ANALYZE on the database after the upgrade which may take a while as it usually needs to read all or almost all of your data. I just recently upgraded a ~1 TB database, the actual upgrade process took less than a minute but analyzing it took much longer.