Re: Accessing Postgres Server and database from other Machine

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Paul Förster <paul(dot)foerster(at)gmail(dot)com>
Cc: "Muthukumar(dot)GK" <muthankumar(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Accessing Postgres Server and database from other Machine
Date: 2020-12-04 16:17:48
Message-ID: 717fd284-6bf5-c5d5-3fed-bb3677108b7a@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)klaver(at)aklaver(dot)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 automatically strip all comments and then diff the result to ones real world postgresql.conf or some other version postgresql.conf file to find parameters that have been removed or changed with a new PostgreSQL version. This is highly useful for planning migrations and have a quick reference what to check for before actually migrating. So for me this is much more 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(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2020-12-04 16:18:39 Re: Set COLLATE on a session level
Previous Message Kevin Brannen 2020-12-04 16:04:34 RE: Alter the column data type of the large data volume table.