Re: Use of non-restart-safe storage by temp_tablespaces

From: "Sven R(dot) Kunze" <srkunze(at)mail(dot)de>
To: Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Jerry Sievers <gsievers19(at)comcast(dot)net>, Mark Dilger <hornschnorter(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Use of non-restart-safe storage by temp_tablespaces
Date: 2017-06-06 13:51:54
Message-ID: 6908d454-80ea-81d2-2a8f-012edf2ee0f4@mail.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06.06.2017 14:31, Bruce Momjian wrote:
> On Tue, Jun 6, 2017 at 04:39:50AM -0300, Alvaro Herrera wrote:
>> I was thinking that you could create the init fork for each unlogged
>> table in a permanent tablespace (probably the default one for the
>> database).
>>
>> FWIW I don't think calling these tablespaces "temporary" is the right
>> word. It's not the tablespaces that are temporary. Maybe "evanescent".
> I was thinking "transient". Amazon uses "ephemeral".
>

Just dropping a translator result here:

[1] results of https://www.dict.cc/deutsch-englisch/fl%C3%BCchtig.html

What about VOLATILE like computer memory (RAM)?

Sven

[1]
volatile {adj}chem.
briefly {adv}
fleeting {adj}
fugitive {adj} [temporary, fleeing]
brief {adj}
cursory {adj}
transient {adj}
vaguely {adv} [look, interested]
transitory {adj}
perfunctory {adj}
hasty {adj}
ephemeral {adj}
fleetingly {adv}
momentary {adj}
evanescent {adj}
passing {adj}
absconded {adj}
casual {adj} [glance, acquaintance etc.]
desultory {adj} [reading]
tangential {adj}
ethereal {adj}chem.
etherial {adj}chem.
flighty {adj}
sketchy {adj} [not detailed]
quick {adj}
perfunctorily {adv}
sketchily {adv}
fugitively {adv}
volatilely {adv}
hit and run {adj}
ephemerally {adv}
non-permanent {adj}
fugacious {adj} [literary]

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-06-06 14:46:05 Re: question about replication docs
Previous Message Albe Laurenz 2017-06-06 13:24:08 Re: Index created in BEFORE trigger not updated during INSERT