On Wed, Jun 27, 2012 at 4:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Wed, Jun 27, 2012 at 4:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> cases where people are modifying the wrong hba file. Can we show
>>> the source text of the hba line?
>> We don't currently keep the full source text around - but we certainly
>> could do that if we wanted to.
> If we're concerned about providing a message like this, I think it'd be
> well worthwhile. We presumably would only store the active lines not
> comment lines, so the extra memory space would be negligible in just
> about any real use-case.
Turned out to be a bit more work than I thought, since the current
parser reads pg_hba byte by byte, and not line by line. So I had to
change that. See attached, seems reasonable?
Description: application/octet-stream (12.8 KB)
In response to
pgsql-hackers by date
|Next:||From: Boszormenyi Zoltan||Date: 2012-06-29 12:43:49|
|Subject: Re: [PATCH 10/16] Introduce the concept that wal has a
|Previous:||From: Magnus Hagander||Date: 2012-06-29 10:22:18|
|Subject: Re: [ADMIN] pg_basebackup blocking all queries with