RE: upgrade questions
От | David Barron |
---|---|
Тема | RE: upgrade questions |
Дата | |
Msg-id | PH0PR22MB33522E9DFF32B1A9E648B5D0E94B2@PH0PR22MB3352.namprd22.prod.outlook.com обсуждение исходный текст |
Ответ на | RE: upgrade questions ("Wetmore, Matthew (CTR)" <Matthew.Wetmore@express-scripts.com>) |
Список | pgsql-admin |
From: Wetmore, Matthew (CTR) <Matthew.Wetmore@express-scripts.com>
Sent: Friday, February 9, 2024 12:12 PM
To: David Barron <david.barron@zencos.com>; pgsql-admin@lists.postgresql.org
Subject: RE: upgrade questions
EXTERNAL SENDER
Since you are updating MAJOR versions, this is what I do before that to have ready, just in case.
(all separate files)
- pg_dump –s
- pg_dump –a
- Pg_dump > *.sql (so human readable)
- cp postgresql.conf > wherever
- shut down pg and tar the /data dir.
There’s more that you can do and this is a little overkill sometimes, but its easier to delete stuff you don’t need after the fact, rather than say , darn, I wish I could look at the schema.
And then there’s the RHEL layer.
Be able to go back to orig RHEL in need of full rollback.
Save off apt-get stuff (versions etc)
Yes, I had assumed I would be doing backups.
В списке pgsql-admin по дате отправления: