From: | Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] VACUUM as a denial-of-service attack |
Date: | 1999-11-29 19:30:51 |
Message-ID: | 199911291930.TAA27498@mtcc.demon.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>
>Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk> writes:
>> In the dim and distant past I produced a patch that put vacuum
>> into the list of things that you could GRANT on a per-table
>
>Thanks for the code, but for now I just threw in a quick pg_ownercheck
>call: VACUUM will now vacuum all tables if you are the superuser, else
>just the tables you own, skipping the rest with a NOTICE. What you had
>looked like more infrastructure than I thought the problem was worth...
>I suspect most people will run VACUUMs from the superuser account
>anyway...
I didn't think it was worth reworking the code, although I may do
just for fun. Your solution is fine.
Keith.
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1999-11-29 20:55:03 | Re: [HACKERS] VACUUM as a denial-of-service attack |
Previous Message | Bruce Momjian | 1999-11-29 19:13:36 | Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions |