From: Joshua D. Drake <jd@commandprompt.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Andres Freund <andres@anarazel.de>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Reviewing freeze map code
Date: Fri, 6 May 2016 14:00:59 -0700
Message-ID: <572D060B.5050503@commandprompt.com> (raw)
In-Reply-To: <20160506205821.GE10850@tamriel.snowman.net>
References: <20160502214818.psk3lmgyihk6gr3k@alap3.anarazel.de>
<20160505000840.epatoq6d2e556446@alap3.anarazel.de>
<CA+TgmobF=86sa=6dF30jaiEFOhZnO+asOB5j69PynPCqtaz9xA@mail.gmail.com>
<572D0309.4090402@commandprompt.com>
<20160506205012.ipuhvctss2ozzs6m@alap3.anarazel.de>
<572D0471.3040009@commandprompt.com>
<20160506205821.GE10850@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 05/06/2016 01:58 PM, Stephen Frost wrote:
> * Joshua D. Drake (jd@commandprompt.com) wrote:
>> 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.
>
> Isn't that exactly what this FORCE option being contemplated would do
> though? Plow through the entire relation, regardless of what the VM
> says is all frozen or not?
>
> Seems like FORCE is a good word for that to me.
Except that we aren't FORCING a vacuum. That is the part I have
contention with. To me, FORCE means:
No matter what else is happening, we are vacuuming this relation (think
locks).
But I am also not going to dig in my heals. If that is truly what
-hackers come up with, thank you at least considering what I said.
Sincerely,
JD
>
> Thanks!
>
> Stephen
>
--
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.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: jd@commandprompt.com, sfrost@snowman.net, andres@anarazel.de, robertmhaas@gmail.com, sawada.mshk@gmail.com
Subject: Re: Reviewing freeze map code
In-Reply-To: <572D060B.5050503@commandprompt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox