Re: Reviewing freeze map code

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Josh berkus <josh(at)agliodbs(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: 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:03:11
Message-ID: 572D068F.3050608@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

JD

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2016-05-06 21:03:53 Re: Reviewing freeze map code
Previous Message Josh berkus 2016-05-06 21:01:34 Re: Reviewing freeze map code