Skip site navigation (1) Skip section navigation (2)

Re: More robust pg_hba.conf parsing/error logging

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: More robust pg_hba.conf parsing/error logging
Date: 2009-09-09 14:18:17
Message-ID: 20090909141817.GC4132@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Rafael Martinez wrote:

> Problem:
> - --------
> If you define in pg_hba.conf a database or a user value with 'ALL'
> instead of 'all', you will lose access to *all* databases involved. The
> reload process will not report anything about 'ALL' been an invalid
> value and the new pg_hba.conf will be reloaded.
> 
> This is the only thing in the log file:
> "LOG:  received SIGHUP, reloading configuration files"

Aye, that's surprising.  I think the correct fix here is to change the
strcmp comparisons to pg_strcasecmp() in several places in hba.c.

(BTW the business about appending newlines to special tokens in
next_token() seems ugly and underdocumented.)

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2009-09-09 14:20:07
Subject: Re: More robust pg_hba.conf parsing/error logging
Previous:From: Pavel StehuleDate: 2009-09-09 14:15:28
Subject: ToDo: array aggregates

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group