Re: Are all unlogged tables in any case truncated after a server-crash?
От | Laurenz Albe |
---|---|
Тема | Re: Are all unlogged tables in any case truncated after a server-crash? |
Дата | |
Msg-id | 371166df102667898df3be4be0e4e07c992f0093.camel@cybertec.at обсуждение исходный текст |
Ответ на | Are all unlogged tables in any case truncated after a server-crash? (sch8el@posteo.de) |
Ответы |
Re: Are all unlogged tables in any case truncated after a server-crash?
|
Список | 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 по дате отправления: