Re: audit table containing Select statements submitted

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: josh(at)agliodbs(dot)com
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, "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 23:00:12
Message-ID: 24186.1147474812@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> 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).

This argument strikes me as nonsense. You've got a utility that's smart
enough to parse the very-free-format message bodies, but it's going to
be too confused by the log line prefix?

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

Hardly minor, as anyone who is so in love with XML that he'd want to use
it for this would likely also have lots of XML tags in his data.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2006-05-12 23:23:32 Re: audit table containing Select statements submitted
Previous Message Tom Lane 2006-05-12 22:52:12 Re: audit table containing Select statements submitted