Le 3 févr. 2016 5:30 PM, "Keith" <keith@keithf4.com> a écrit :
>
>
>
> On Wed, Feb 3, 2016 at 7:42 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
>>
>> Stephen Tahmosh wrote:
>> > Is there any case where this data, in an unlogged table, would persist through a server “crash”?
>> > (however caused).
>>
>> No.
>> That is the price you pay for avoiding transaction logs.
>>
>> Yours,
>> Laurenz Albe
>>
>> --
>> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-admin
>
>
> If you upgrade to 9.5, you can take advantage of the fact that you can convert an unlogged table to a logged one with an ALTER TABLE statement. I believe this does a full rewrite of the table again, but you may be able to incorporate that into your ETL process if it ends up still being quicker than doing the ETL directly on a normal table.
>
> http://www.postgresql.org/docs/9.5/static/sql-createtable.html#SQL-CREATETABLE-UNLOGGED
>
It doesn't rewrite the whole table, but it puts its whole content in the WAL files.