Re: Are all unlogged tables in any case truncated after a server-crash? - Mailing list pgsql-general

From Laurenz Albe
Subject Re: Are all unlogged tables in any case truncated after a server-crash?
Date
Msg-id 371166df102667898df3be4be0e4e07c992f0093.camel@cybertec.at
Whole thread Raw
In response to Are all unlogged tables in any case truncated after a server-crash?  (sch8el@posteo.de)
Responses Re: Are all unlogged tables in any case truncated after a server-crash?  (sch8el@posteo.de)
List pgsql-general
On Thu, 2021-11-11 at 18:39 +0000, sch8el@posteo.de wrote:
> every few weeks I use Postgres ability, to import huge data sets very 
> fast by means of "unlogged tables". The bulk load (consisting of plenty 
> "copy"- & DML-Stmts) and the spatial index creation afterwards, takes 
> about 5 hours on a proper server  (pg12.7 & PostGIS-Extension). After 
> that all unlogged tables remain completely unchanged (no 
> DML-/DDL-Statements). Hence all of my huge unlogged, "static" tables get 
> never "unclean" and should not be truncated after a server crash.

There is no way to achieve that.

But you could keep the "huge data sets" around and load them again if
your server happens to crash (which doesn't happen often, I hope).

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com




pgsql-general by date:

Previous
From: "孤傲小二~阿沐"
Date:
Subject: sqrt_bigint_v2
Next
From: sch8el@posteo.de
Date:
Subject: Re: Are all unlogged tables in any case truncated after a server-crash?