|From:||Bruce Momjian <bruce(at)momjian(dot)us>|
|Cc:||PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>|
|Subject:||Re: Adding a concept of TEMPORARY TABLESPACE for the use in temp_tablespaces|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Thu, Mar 14, 2019 at 12:53:02AM -0700, Mitar wrote:
> On Fri, Jan 25, 2019 at 2:32 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > I wrote a blog entry about this:
> > https://momjian.us/main/blogs/pgblog/2017.html#June_2_2017
> > This is certainly an area we can improve, but it would require changes
> > in several parts of the system to handle cases where the tablespace
> > disappears.
> Yes, I read the discussion thread you point at the end of your blog
> post.  This is why I posted an e-mail to the mailing list because
> some statements from that thread do not hold anymore. For example, in
> the thread it is stated:
> "Just pointing the tablespace to non'restart'safe storage will get you
> an installation that fails to boot after a restart, since there's a
> tree structure that is expected to survive, and when it's not found,
> postgres just fails to boot."
> This does not seem to be true (anymore?) based on my testing. You get
> noise in logs, but installation boots without a problem.
> So maybe we are closer to this than we realize?
Interesting. What happens when you references objects that were in the
tablespace? What would we want to happen?
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
|Next Message||Tsunakawa, Takayuki||2019-04-09 00:23:45||RE: reloption to prevent VACUUM from truncating empty pages at the end of relation|
|Previous Message||Kyotaro HORIGUCHI||2019-04-09 00:04:04||Re: Problem with default partition pruning|