| From: | "Keith Worthington" <keithw(at)narrowpathinc(dot)com> |
|---|---|
| To: | PostgreSQL Novice <pgsql-novice(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: [NOVICE] Question on TRUNCATE privleges |
| Date: | 2005-02-24 22:28:08 |
| Message-ID: | 20050224222631.M29042@narrowpathinc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-novice |
On Thu, 24 Feb 2005 17:15:42 -0500, Tom Lane wrote
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Uh, that seems like it adds extra complexity just for this single case.
>
> Yeah. I've dropped the idea personally -- the suggestion that the table
> owner can provide a SECURITY DEFINER procedure to do the TRUNCATE if
> he wants to allow others to do it seems to me to cover the problem.
Could someone point me in the direction of documentation on this SECURITY
DEFINER feature?
Kind Regards,
Keith
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-02-24 22:28:44 | Re: [PATCHES] [pgsql-hackers-win32] Repleacement for src/port/snprintf.c |
| Previous Message | Bruce Momjian | 2005-02-24 22:27:25 | Re: [PATCHES] [pgsql-hackers-win32] Repleacement for src/port/snprintf.c |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-02-24 22:47:44 | Re: [NOVICE] Question on TRUNCATE privleges |
| Previous Message | Bruce Momjian | 2005-02-24 22:21:29 | Re: [NOVICE] Question on TRUNCATE privleges |