Search Postgresql Archives
Re: Are all unlogged tables in any case truncated after a server-using
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: Are all unlogged tables in any case truncated after a server-using
From
: Michael Lewis <mlewis@xxxxxxxxxxx>
Date
: Fri, 12 Nov 2021 07:00:42 -0700
Cc
: Laurenz Albe <laurenz.albe@xxxxxxxxxxx>, pgsql-general <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to
: <
41f67000-8ddc-a9ab-c6af-097af084498d@posteo.de
>
References
: <
c9f8b3a5-eb45-d3f6-9fd6-2e1d032eea12@posteo.de
> <
371166df102667898df3be4be0e4e07c992f0093.camel@cybertec.at
> <
41f67000-8ddc-a9ab-c6af-097af084498d@posteo.de
>
Why keep them as unlogged tables? If data is static, can you spare the disk space to gradually copy data from existing unlogged table to new copy that is logged, and then have brief exclusive lock to drop unlogged and rename new one?
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
References
:
Are all unlogged tables in any case truncated after a server-crash?
From:
sch8el
Re: Are all unlogged tables in any case truncated after a server-crash?
From:
Laurenz Albe
Re: Are all unlogged tables in any case truncated after a server-crash?
From:
sch8el
Prev by Date:
Re: Pg_hba.conf problem after unexpected IP change
Next by Date:
Replace anonymized data in string
Previous by thread:
Re: Are all unlogged tables in any case truncated after a server-crash?
Next by thread:
Re: Are all unlogged tables in any case truncated after a server-crash?
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]
