On 6/30/2017 9:18 AM, Manjula Bharathan wrote:
> We have been seeing issues with our Postgres Primary /Master server,
> where we see the following message logged to the log file
> *** glibc detected *** postgres: SELECT: double free or corruption
> (!prev): 0x0000000001e59de0 ***
>
> This has happened thrice in the last week , twice last Sunday June
> 25th and once on Thursday June 29th.
> and the query causing the termination twice on June 25th was the same
> . The query on June 29th was a different one.
> Note: We recently upgraded postgresql version to 9.6.3 from version
> 9.5 on June 21st.. We did not encounter this error before the Upgrade.
> Operating System : CentOS release 6.6
CentOS 6 update 6 is several releases behind, you are missing about 18
months of security and bug fixes.... 6.9 is current
what version kernel and glibc are you running?
glibc-2.12-1.209, kernel-2.6.32-696.3.2 are the latest for CentOS 6
doing partial OS upgrades, where you update only some system components
takes you into uncharted territory, as only the complete latest set of
system packages is tested together, mixing newer system packages with
older components is risky and unsupported.
--
john r pierce, recycling bits in santa cruz
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs