Re: audit table containing Select statements submitted

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "Hogan, James F(dot) Jr(dot)" <JHogan(at)seton(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: audit table containing Select statements submitted
Date: 2006-05-12 18:20:41
Message-ID: 200605121120.42118.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew,

> The real problem is the message, which is now
> from the logging code's point of view basically an opaque string.
> Changing that would be a massive undertaking, especially when you think
> of the effect on the translators.

Hmmm ... I don't see this as a problem. Just stick the whole message into
a single XML field. This is one area where XML is easier that SQL; since
it's a document format, it has no problem with a great big blob of text.
"Unstructured Data" and all that nonsense.

Then whatever utility the user uses to *read* the XML can parse the message
according to the user's desires. It'll still be an improvement over the
current format for log digestion, since it will become easy to separate
the message from the prefix and tag (which currently it's not).

The only real issue I see is the possibility of XML codes embedded in the
text, but that seems minor.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-05-12 18:43:56 Re: audit table containing Select statements submitted
Previous Message Andrew Dunstan 2006-05-12 18:05:33 Re: audit table containing Select statements submitted