| From: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
|---|---|
| To: | Yves Dorfsman <yves(at)zioup(dot)com> |
| Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: unlogged tables |
| Date: | 2015-04-13 20:40:33 |
| Message-ID: | CAJghg4K1WGkQ7j+FqPWaUBWzzJC-uW7gqq1Ap4=nU2peB1WPcQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Apr 13, 2015 at 5:30 PM, Yves Dorfsman <yves(at)zioup(dot)com> wrote:
>
> In my experience postgres is very aggressive in getting rid of unlogged
> tables, it does get rid of them from shutdowns that seem perfectly fine (no
> crash). A lot of people get surprised by this.
Shutdowns in "fast" or "smart" modes does not get rid of unlogged tables.
But if you do "immediate", then it does, and I don't see why people get
surprised by it, as you probably shouldn't be using "immediate" mode in
normal circumstances.
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 | David G. Johnston | 2015-04-13 20:49:16 | Re: unlogged tables |
| Previous Message | Yves Dorfsman | 2015-04-13 20:30:49 | Re: unlogged tables |