Re: Accessing Postgres Server and database from other Machine - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Accessing Postgres Server and database from other Machine
Date
Msg-id 717fd284-6bf5-c5d5-3fed-bb3677108b7a@aklaver.com
Whole thread Raw
In response to Re: Accessing Postgres Server and database from other Machine  (Paul Förster <paul.foerster@gmail.com>)
Responses Re: Accessing Postgres Server and database from other Machine
List pgsql-general
On 12/4/20 8:03 AM, Paul Förster wrote:
> Hi Adrian,
> 
>> On 04. Dec, 2020, at 16:13, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>> That is the wrong file, the *.sample is the giveaway.
> 
> hmmm, I'd rather call it essential reference documentation or template for automation. It's perfectly well suited to
automaticallystrip all comments and then diff the result to ones real world postgresql.conf or some other version
postgresql.conffile to find parameters that have been removed or changed with a new PostgreSQL version. This is highly
usefulfor planning migrations and have a quick reference what to check for before actually migrating. So for me this is
muchmore than just a giveaway.
 
> 

Yes, but for changing the behavior of a running instance it is the wrong 
file and it's extension is a clue.


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Kevin Brannen
Date:
Subject: RE: Alter the column data type of the large data volume table.
Next
From: Tom Lane
Date:
Subject: Re: Set COLLATE on a session level