| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL crash with PANIC message |
| Date: | 2016-03-24 04:12:00 |
| Message-ID: | CAB7nPqTAtMLDFz8MixM43VcJbqU1o1D8xxeiQYJg8y_bRKvvcw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Mar 24, 2016 at 5:57 AM, Adrian Klaver
<adrian(dot)klaver(at)aklaver(dot)com> wrote:
> On 03/23/2016 12:02 PM, Moreno Andreo wrote:
>>
>> Il 23/03/2016 19:57, Adrian Klaver ha scritto:
>>>
>>>
>>> Might help to look in:
>>>
>>> Control Panel --> Administrative Tools --> Event Viewer
>>
>>
>> No help there. Nothing strange or pointing to critical resource usage.
>
>
> The only thing I have left is the generic answer for when things act funny
> on Windows:
>
> Do you have AntiVirus software running against the Postgres data directory?
That's likely the reason, something creeping behind is forcing
disconnections from the server.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavlov, Vladimir | 2016-03-24 07:54:25 | Multixacts wraparound monitoring |
| Previous Message | David G. Johnston | 2016-03-24 02:15:41 | Re: Only owners can ANALYZE tables...seems overly restrictive |