On Thu, 2006-01-05 at 09:41 -0500, Stephen Frost wrote:
> * Michael Paesold ([EMAIL PROTECTED]) wrote:
> > 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.
>
> Oh, I thought the reliability bit would bypass WAL even with archiving
> turned on (which could be fine in some cases, just not all cases :). Of
It might be better if this was an setting in postgresql.conf requiring a
restart to change, off by default.
I don't like the thought of a table owner or even a super-user being
able to throw away data because they failed to investigate the full
impact of the backup strategy. I.e. Someone missed the memo that backups
were changing from pg_dumps to PITR for database environment H.
--
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
