| From: | scott ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: RemoveIPC problem |
| Date: | 2017-09-01 03:10:20 |
| Message-ID: | 12ED99C4-6965-4C06-BDDD-E83106DD3835@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yeah, I was kind of thinking that PG detects the semaphore not existing, bails immediately, restarts clean, thus no problem. I just wanted to hear from people, like you, that know way more than I do about the internals.
> On Aug 31, 2017, at 9:08 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> scott ribe <scott_ribe(at)elevated-dev(dot)com> writes:
>> Thanks to a typo, I did not turn off systemd's RemoveIPC, and had many many pg restarts before I figured out the problem.
>
>> Should my data be OK? Or do I need to dump & reload?
>
> I don't know of any reason to think that that poses a data corruption
> risk. (But I've been wrong before.)
>
> regards, tom lane
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
(303) 722-0567
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-09-01 03:48:09 | Re: RemoveIPC problem |
| Previous Message | Tom Lane | 2017-09-01 03:08:21 | Re: RemoveIPC problem |