Re: Truncating/vacuuming relations on full tablespaces - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Truncating/vacuuming relations on full tablespaces
Date
Msg-id CACjxUsN+HQCuW5A4JNd8PeBfR4xv8PhY5ifNkt-PsWXfgHB4dw@mail.gmail.com
Whole thread Raw
In response to Re: Truncating/vacuuming relations on full tablespaces  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Truncating/vacuuming relations on full tablespaces
List pgsql-hackers
On Fri, Jan 15, 2016 at 11:41 AM, Robert Haas <robertmhaas@gmail.com> wrote:

> Anybody else want to weigh in with thoughts on any of this?

Leaving aside VACUUM issues for a moment, what problems to you see
with an empty table that has no visibility map or free space map
fork?  In other words, for the TRUNCATE case we could either skip
these if there is an error, or not even try to build them at all.
Either seems better than the status quo.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Death by regexp_replace
Next
From: Robert Haas
Date:
Subject: Re: Truncating/vacuuming relations on full tablespaces