From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Virendra Kumar <viru_7683(at)yahoo(dot)com> |
Cc: | Pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Back Port Request for INVALID Startup Packet |
Date: | 2020-03-12 00:29:27 |
Message-ID: | 10013.1583972967@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Virendra Kumar <viru_7683(at)yahoo(dot)com> writes:
> Can you please back port patch where if a 0 byte packet sent to PG instance (Health Checks), it starts complaining about invalid startup packet and flood the log which increases log size considerably if the health checks are every 3 seconds or something like that.
> Patch Requested - https://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=342cb650e
We generally don't like to change behavior of back branches without
ironclad agreement that the existing behavior is a bug ... which this
surely isn't. Also, the discussion leading up to that patch specifically
considered and rejected back-patching; so I'm disinclined to overrule
that decision now.
I would suggest that an every-three-second health check is not
appropriate, especially one that is so minimal that it only
detects whether the postmaster is alive.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | AC Gomez | 2020-03-12 00:46:20 | encrypt/decrypt between javascript and postgresql. |
Previous Message | Adrian Klaver | 2020-03-12 00:11:08 | Re: pg_restore restores out of order |