| From: | David Barron <david(dot)barron(at)zencos(dot)com> |
|---|---|
| To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: upgrade questions |
| Date: | 2024-02-09 18:09:36 |
| Message-ID: | PH0PR22MB335248AF89C51EBEAC63BFD1E94B2@PH0PR22MB3352.namprd22.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
-----Original Message-----
From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
Sent: Friday, February 9, 2024 12:08 PM
To: David Barron <david(dot)barron(at)zencos(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: upgrade questions
EXTERNAL SENDER
> On Feb 9, 2024, at 10:00 AM, David Barron <david(dot)barron(at)zencos(dot)com> wrote:
>
> I’ve also seen references to copying over the pg_hba.conf and postgresql.conf files from the old data directory to the new.
>Then you will be getting default values for the many, many parameters added to postgresql.conf between 11 & 15--and will have no explanatory entries documenting them. A >much better suggestion is to diff the two, and apply customizations from the old to the new. (Also skim release notes for any that have been mooted.)
That's a good point I had not considered.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Barron | 2024-02-09 18:10:21 | RE: upgrade questions |
| Previous Message | Ron Johnson | 2024-02-09 17:43:03 | Re: upgrade questions |