From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Josh berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Reviewing freeze map code |
Date: | 2016-05-06 21:08:06 |
Message-ID: | 20160506210806.f6pnk6ueirjqrlmu@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2016-05-06 14:03:11 -0700, Joshua D. Drake wrote:
> On 05/06/2016 02:01 PM, Josh berkus wrote:
> > On 05/06/2016 01:58 PM, Andres Freund wrote:
> > > On 2016-05-06 13:54:09 -0700, Joshua D. Drake wrote:
> > > > On 05/06/2016 01:50 PM, Andres Freund wrote:
> >
> > > > > There already is FREEZE - meaning something different - so I doubt it.
> > > >
> > > > Yeah I thought about that, it is the word "FORCE" that bothers me. When you
> > > > use FORCE there is an assumption that no matter what, it plows through
> > > > (think rm -f). So if we don't use FROZEN, that's cool but FORCE doesn't work
> > > > either.
> > >
> > > SCANALL?
> > >
> >
> > VACUUM THEWHOLEDAMNTHING
> >
>
> I know that would never fly but damn if that wouldn't be an awesome keyword
> for VACUUM.
It bothers me more than it probably should: Nobdy tests, reviews,
whatever a complex patch with significant data-loss potential. But as
soon somebody dares to mention an option name...
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2016-05-06 21:08:16 | Re: Reviewing freeze map code |
Previous Message | Jeff Janes | 2016-05-06 21:06:33 | Re: atomic pin/unpin causing errors |