Re: Storing original rows before update or delete - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Storing original rows before update or delete
Date
Msg-id CA+TgmoZxJm8Q6PK-BkwoA4K2u=49u=a9TJT=QczLc5Lh4moNjg@mail.gmail.com
Whole thread Raw
In response to Re: Storing original rows before update or delete  (Miroslav Šimulčík <simulcik.miro@gmail.com>)
List pgsql-hackers
2011/11/4 Miroslav Šimulčík <simulcik.miro@gmail.com>:
> If I restrict any DML operation to internal tables (history tables) in phase
> of parse analyze, nobody can do such operation regardless of user rights.

There is absolutely zero point in trying to prevent the superuser from
doing whatever they want.  The superuser has many, many ways of
bypassing whatever controls you put in place - e.g. loading custom C
code into the backend, whacking around the system catalogs, etc.

> However, triggers can't be used in this case.

Which is another reason not to do it that way.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: DeArchiver process
Next
From: Magnus Hagander
Date:
Subject: Show statistics target in \d+