| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Melvin Davidson <melvin(dot)davidson(at)rackspace(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Feature / Enhancement request. |
| Date: | 2009-08-25 18:12:04 |
| Message-ID: | 3073cc9b0908251112s67bcdc67q2cfeefac6171aa0e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 25, 2009 at 11:18 AM, Melvin
Davidson<melvin(dot)davidson(at)rackspace(dot)com> wrote:
>
> This would be very useful for user tables that are meant to exist for only a
> specific length of time. eg: 1 month.
>
that's a weird concept
>
> Likewise, relmoddat would be useful for determining when someone made
> changes to a table, index, view, etc.
>
i agree it could be useful for auditing porpouses... in fact, in
environments like government it's likely the law who wants such a
functionality...
but instead of new fields we can invent a new catalog for that and we
can use a guc to enable/disable the track of such changes
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-08-25 18:19:19 | Re: SET syntax in INSERT |
| Previous Message | Pavel Stehule | 2009-08-25 17:36:40 | Re: SET syntax in INSERT |