| From: | "Michael Paesold" <mpaesold(at)gmx(dot)at> |
|---|---|
| To: | "Stephen Frost" <sfrost(at)snowman(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] TRUNCATE, VACUUM, ANALYZE privileges |
| Date: | 2006-01-05 14:37:32 |
| Message-ID: | 01ac01c61205$90796890$0f01a8c0@zaphod |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Stephen Frost wrote:
> I'm not a particularly big fan of this though because, while I'd
> like to be able to give TRUNCATE permissions I'm not a big fan of SET
> RELIABILITY because it would affect PITR backups.
As far as I have understood the discussion... with WAL archiving turned on,
the whole RELIABILITY changes would be no-ops, no?
Just as the CTAS optimization etc. only skip WAL if WAL archiving is turned
off.
Best Regards,
Michael Paesold
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2006-01-05 14:41:47 | Re: [PATCHES] TRUNCATE, VACUUM, ANALYZE privileges |
| Previous Message | Stephen Frost | 2006-01-05 14:04:06 | Re: [PATCHES] TRUNCATE, VACUUM, ANALYZE privileges |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2006-01-05 14:41:47 | Re: [PATCHES] TRUNCATE, VACUUM, ANALYZE privileges |
| Previous Message | Stephen Frost | 2006-01-05 14:04:06 | Re: [PATCHES] TRUNCATE, VACUUM, ANALYZE privileges |