If we're looking at this, we might want to look at how apache does it with
it's customlog feature. This allows you to first define custom log types,
then set them according to which virtual server you're setting up.
I could see that being nice so you could create a couple of different
custom log types, then use one for one database, and another for a
different database.
For people running large numbers of databases on a single cluster, it
might be quite useful to be able to log each database differently.
On Tue, 5 Aug 2003, Bruce Momjian wrote:
>
> Another interesting idea, if we do a single log variable with parameters
> separated by commas, is to allow some syntax where you could specify the
> delimiter between fields, so it could be:
>
> log_line: "|", dbname, username
>
> or
>
> log_line: " ", dbname, username
>
> ---------------------------------------------------------------------------
>
> Josh Berkus wrote:
> > Tom,
> >
> > > > I'm prepared to be guided by concensus, though.
> > >
> > > I'm not dead set on it either, just wanted to raise a flag. Who else
> > > has an opinion?
> >
> > >From my perspective, we could really use a "delimiter" between the "fields" of
> > log output which is unlikely to appear within those fields instead of parsing
> > by character count, rather than making dbname a special case.
> >
> > Or do we already do this and I'm not parsing my log right?
> >
> > --
> > Josh Berkus
> > Aglio Database Solutions
> > San Francisco
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 8: explain analyze is your friend
> >
>
>
