Re: Logging (was Re: Suggestion GRANT ALTER, TRIGGER ON ALTER)

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: <josh(at)agliodbs(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>, "David Fetter" <david(at)fetter(dot)org>
Subject: Re: Logging (was Re: Suggestion GRANT ALTER, TRIGGER ON ALTER)
Date: 2003-05-21 01:53:04
Message-ID: 095c01c31f3b$b7d02970$6500a8c0@fhp.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Strikes me as a tad unwieldy --- the useful cases would correspond to
> very long log_statement lists, and in every new release the list would
> change. It's probably better to have a very small number of categories,
> something like
> SELECT
> INSERT/UPDATE/DELETE
> all DDL
> and be able to flip logging on/off per category. But we need to think
> about exactly what the categories are.

How about 'log to table' like Oracle can (apparently) do. All sorts of
problems I can think with it, but then at least people can just query it
using normal SQL.

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2003-05-21 02:45:32 Free Space?
Previous Message Christopher Kings-Lynne 2003-05-21 01:51:12 Re: Suggestion GRANT ALTER, TRIGGER ON ALTER