From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | simon(at)2ndquadrant(dot)com, pgman(at)candle(dot)pha(dot)pa(dot)us, kleptog(at)svana(dot)org, gsstark(at)mit(dot)edu, pg(at)rbt(dot)ca, zhouqq(at)cs(dot)toronto(dot)edu, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and |
Date: | 2005-12-30 14:57:06 |
Message-ID: | 11876.1135954626@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> Simon Riggs said:
>> Following Andrew's concerns, I'd also note that ALTER TABLE requires a
>> much higher level of privilege to operate than does COPY. That sounds
>> like it will make things more secure, but all it does is open up the
>> administrative rights, since full ownership rights must be obtained
>> merely to load data.
> My concern is more about making plain that this is for special operations,
> not normal operations. Or maybe I have misunderstood the purpose.
Rephrase that as "full ownership rights must be obtained to load data in
a way that requires dropping any existing indexes and locking out other
users of the table". I don't think the use-case for this will be very
large for non-owners, or indeed even for owners except during initial
table creation; and so I don't think the above argument is strong.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2005-12-30 15:07:25 | Re: Removing SORTFUNC_LT/REVLT |
Previous Message | Andrew Dunstan | 2005-12-30 14:53:33 | Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and |