Andrew Dunstan wrote: > Bruce Momjian said: > > DROP would drop the table on a restart > > after a non-clean shutdown. It would do _no_ logging on the table and > > allow concurrent access, plus index access. DELETE is the same as > > DROP, but it just truncates the table (perhaps TRUNCATE is a better > > word). > > > > EXCLUSIVE would allow only a single session to modify the table, and > > would do all changes by appending to the table, similar to COPY LOCK. > > EXCLUSIVE would also not allow indexes because those can not be > > isolated like appending to the heap. EXCLUSIVE would write all dirty > > shared buffers for the table and fsync them before committing. SHARE > > is the functionality we have now, with full logging. > > > I an horribly scared that this will be used as a "performance boost" for > normal use. I would at least like to see some restrictions that make it > harder to mis-use. Perhaps restrict to superuser?
Certainly restrict to table owner. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
