From: | Keith <keith(at)keithf4(dot)com> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | "Stephen Tahmosh *EXTERN*" <stahmosh(at)shieldsrx(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Re: Postgres 9.4 unlogged table. Under any circumstance after server crash would data persist? |
Date: | 2016-02-03 16:28:11 |
Message-ID: | CAHw75vtzSCpziH9-UcZqotEzeBYWZk9FmBbOaiKFgXFq=m1ukQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Feb 3, 2016 at 7:42 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)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(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2016-02-03 17:08:43 | Re: Re: Postgres 9.4 unlogged table. Under any circumstance after server crash would data persist? |
Previous Message | Tom Lane | 2016-02-03 15:47:40 | Re: invalid memory alloc request size 18446744073709551614 |