Re: Syslog Facility Patch

From: Larry Rosenman <ler(at)lerctr(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Syslog Facility Patch
Date: 2000-11-14 22:54:59
Message-ID: 20001114165459.A16010@lerami.lerctr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Larry Rosenman <ler(at)lerctr(dot)org> [001114 16:06]:
> * Peter Eisentraut <peter_e(at)gmx(dot)net> [001114 16:03]:
> > Larry Rosenman writes:
> >
> > > log_connections = on
> > > fsync = off
> > > #max_backends = 64
> > > syslog_facility = LOCAL5.3we4rwjtasrtuert
> >
> > It's the dot. The regular expression needs some work. Make a note to
> > always test with identical values next time. :-)
> OK, so the parser needs help? Can I try and fix it? What DON'T we
> want guc-file.l to accept for a string?
Ok, so what I think(?) needs to happen is the FIXME: tag needs to be
handled. We need to code a version of src/backend/parser/scansup.c
that doesn't use palloc, and also strips the apostrophes from the
front and end of the string? This doesn't look that hard. Do I have
"permission" to play with it, and submit a patch when I've got it
fixed?

I ass/u/me we want to allow any of the 'C' escapes? or just
a-zA-Z0-9-. for a GUC_STRING?
>
>
> >
> > > syslog_progid = pgtest
> > > syslog=2
> > > showportnumber = on
> >
> > --
> > Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
>
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 972-414-9812 (voice) Internet: ler(at)lerctr(dot)org
> US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-14 23:14:07 Re: Re: Commit finished?
Previous Message Philip Warner 2000-11-14 22:34:50 Re: Details for planned template0/template1 change