Re: Unlogged vs. In-Memory - Mailing list pgsql-advocacy

From Kevin Grittner
Subject Re: Unlogged vs. In-Memory
Date
Msg-id 4DC00893020000250003D1F4@gw.wicourts.gov
Whole thread Raw
In response to Re: Unlogged vs. In-Memory  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Unlogged vs. In-Memory
List pgsql-advocacy
Magnus Hagander <magnus@hagander.net> wrote:

> They are *not* similar to in-memory table, in that they are
> *always* written to disk.

I thought we avoided flushing them to disk on checkpoint, or did
that idea fall flat?  Does the background writer flush them?  If
neither of these happens, then we can legitimately call them
in-memory, as long as we point out that they are saved on a clean
shutdown for reload on startup, and may be flushed from RAM at times
when other objects need the memory.

-Kevin

pgsql-advocacy by date:

Previous
From: Dave Page
Date:
Subject: Re: Unlogged vs. In-Memory
Next
From: Josh Berkus
Date:
Subject: Re: Unlogged vs. In-Memory