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

From Nicklas Avén
Subject Re: Accessing Postgres Server and database from other Machine
Date
Msg-id 450B1DA0-91E3-43E9-873A-82E89A655AC5@jordogskog.no
Whole thread Raw
In response to Re: Accessing Postgres Server and database from other Machine  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: Accessing Postgres Server and database from other Machine
Re: Accessing Postgres Server and database from other Machine
List pgsql-general

On 4 December 2020 17:17:48 CET, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>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 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.


You will prabably also need to change in tge pg_hba.conf file. At least in linux there is no entry for connections from
theoutside there. You will need a "host" entry accepting any ip address or specify what ip your collegue is connecting
fromif possible. I have missed this step a few times and banged my head.  

/Nicklas



pgsql-general by date:

Previous
From: Olivier Gautherot
Date:
Subject: Re: Alter the column data type of the large data volume table.
Next
From: Michael Lewis
Date:
Subject: Extended statistics for correlated columns, row estimates when values are not in MCVs list