From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
---|---|
To: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
Cc: | Hemil Ruparel <hemilruparel2002(at)gmail(dot)com>, "Muthukumar(dot)GK" <muthankumar(at)gmail(dot)com>, Nicklas Avén <nicklas(dot)aven(at)jordogskog(dot)no>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Adrian Klaver <adrian(dot)klaver(at)aklaver(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-05 11:44:15 |
Message-ID: | 808DF8CC-EE50-4CB4-BFA1-69E62D7A8F08@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 5 Dec 2020, at 10:05, Paul Förster <paul(dot)foerster(at)gmail(dot)com> wrote:
>
> Hi Hemil,
>
>> On 05. Dec, 2020, at 07:50, Hemil Ruparel <hemilruparel2002(at)gmail(dot)com> wrote:
>>
>> Did you restart postgres after changing pg_hba.conf?
>
> that shouldn't be necessary for changes in pg_hba.conf. Just do either on the command line:
>
> $ pg_ctl reload
While you’re in there, also verify that something is listening on the port (see below)
$ netstat -an
> or from psql:
>
> postgres=# select pg_reload_conf();
>
> You can then see the effective result immediately in pg_hab_file_rules:
>
> postgres=# table pg_hba_file_rules;
Also:
postgres=# show listen_addresses;
postgres=# show port;
Those will tell you whether the server is listening on the network and on the expected port.
Alban Hertroys
--
There is always an exception to always.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-12-05 12:12:15 | Re: Set COLLATE on a session level |
Previous Message | charles meng | 2020-12-05 10:38:40 | Re: Alter the column data type of the large data volume table. |