| From: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
|---|---|
| To: | dgabriel <gabriel(dot)dodan(at)gmail(dot)com> |
| Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: unlogged tables |
| Date: | 2015-04-13 19:36:10 |
| Message-ID: | CAJghg4+NoOaip1VaBK9+cY-LYjmUr_9kFNZ3sdWq5wQRNVc9HA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Apr 13, 2015 at 4:31 PM, dgabriel <gabriel(dot)dodan(at)gmail(dot)com> wrote:
> "In the event of a normal shutdown, we can flush all the writes to disk
> so we know all the data has been written, so there is no need to truncate."
>
> Isn't possible to periodically flush data to disk and in case of crush
> postgres to load only the data that existed at last flush? The periodic
> flush could be configurable, for example every 30 minutes or after x rows
> updated/inserted.
>
There is no such facility implemented for UNLOGGED TABLEs. That could be a
feature request though.
Best regards,
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dgabriel | 2015-04-13 20:16:14 | Re: unlogged tables |
| Previous Message | dgabriel | 2015-04-13 19:31:42 | Re: unlogged tables |