| From: | "ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com> |
|---|---|
| To: | George Neuner <gneuner2(at)comcast(dot)net>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Unlogged tables |
| Date: | 2017-08-09 18:30:10 |
| Message-ID: | BN4PR15MB0547F5864AD9691E31458FE1858B0@BN4PR15MB0547.namprd15.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Ok, I am not sure. I run Postgres as a service, and when my Windows rebooted after a patch, UNLOGGED tables were cleaned... maybe the patch process in Windows messed something up, I don't know.
From: gneuner2(at)comcast(dot)net
Sent: August 9, 2017 13:17
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Unlogged tables
On Wed, 9 Aug 2017 09:14:48 -0700, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>Why doesn't the Windows scheduled shutdown signal postgres to shutdown
>cleanly and wait for it to do so? That is what is supposed to happen.
Windows *does* signal shutdown (and sleep and hibernate and wakeup).
pg_ctl can catch these signals only when running as a service ... it
will not catch any system signals when run as an application.
George
--
Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
| From | Date | Subject | |
|---|---|---|---|
| Next Message | George Neuner | 2017-08-09 19:52:26 | Re: Unlogged tables |
| Previous Message | George Neuner | 2017-08-09 18:15:37 | Re: Unlogged tables |