Re: pg_hba_lookup function to get all matching pg_hba.conf entries - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: pg_hba_lookup function to get all matching pg_hba.conf entries
Date
Msg-id CAFj8pRC5zbkUMUf=y4fS8Of3qv4nVuAJBjn6MEjJYa+=Yem3mw@mail.gmail.com
Whole thread Raw
In response to Re: pg_hba_lookup function to get all matching pg_hba.conf entries  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers


2015-12-04 17:34 GMT+01:00 Alvaro Herrera <alvherre@2ndquadrant.com>:
Pavel Stehule wrote:

> It should be disabled by default
>
> only when you have some problems, then you can enable it

That still seems mostly unworkable to me.  Are we going to tell DBAs to
set PGOPTIONS when they have some pg_hba problem?

why not - it isn't bad idea.
 

What's the issue with calling the function when you want to research
some problem?  Presumably that's the whole point of the function.

sometimes you shouldn't set real parameters - I had to solve some issues with IP6/IP4 - and I missed debug info on server side.

Regards

Pavel
 

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Random crud left behind by aborted TAP tests
Next
From: Jehan-Guillaume de Rorthais
Date:
Subject: Replication stats from slaves