On 17 October 2010 02:27, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > Hmm. Would it be possible to list keywords _applicable_ to each field, > and have these passed down to next_token by the caller instead? This > seems backwards, but I'm not sure if the other way is really workable. >
Short answer: I don't think it is workable, or I would have done it that way in the first place. Full answer: The problem is that pg_hba.conf doesn't have a fixed structure. Each line can be 4, 5 or 6 fields (not including the final 'options' field) long, and which of these structures apply to any given line isn't decided until parse_hba_line goes to work on it. At the time that next_token gets called, we have no way of knowing which field is currently being tokenised, at least not without doing some serious rearrangement of hba.c, so that it tokenises and then parses one token at a time, instead of tokenising the whole file and then parsing all the lines. Cheers, BJ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
