| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Zlatko Mati? <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr> |
| Cc: | Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to set an expiration date for a WHOLE user account |
| Date: | 2005-06-15 14:11:15 |
| Message-ID: | 20050615141115.GA7595@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jun 15, 2005 at 13:34:39 +0200,
Zlatko Mati? <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr> wrote:
> Hi.
> Concerning Együd's question, I also wanted to ask about setting expiration
> date for database. But, I would like to set validity in sense of certain
> actions.
> For example, I would like to prevent adding new records after expiration,
> but would allow viewing existing records....
> Is there any way to acomplish that?
Possibly you could do what you want by using AFTER triggers on all of the
tables. This will only be practical if the users with update access do
not own the tables.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-15 14:23:12 | Re: Deadlock Problem |
| Previous Message | Bruce Momjian | 2005-06-15 14:10:40 | Re: Autovacuum in the backend |