| From: | Олег Самойлов <splarv(at)ya(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL lock file |
| Date: | 2019-08-12 11:47:32 |
| Message-ID: | 9C1CF14F-DBB7-4AF1-A42D-28B4ADFF0556@ya.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Best practice for this sort of thing is considered to be to run the two
> Postgres instances under different user IDs. That avoids them thinking
> that the other one's lock files are relevant, and it provides an extra
> layer of security against possible conflicts between the two instances.
>
> regards, tom lane
Thanks, an interesting notice. I already did changes in start script to check instance by pg_ctl status and delete lock file if status<>0. But your recommendation is looked better.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2019-08-12 12:24:00 | Re: How to gracefully keep my specific index in memory ? |
| Previous Message | James (王旭) | 2019-08-12 09:51:34 | How to gracefully keep my specific index in memory ? |