balance the reading by pgpool? Should all readings go to the
replicas? or reading goes to all nodes?
Regards,
Glauco Torres
>
> Might be worth comparing sha1sum's of the postgres executable between
> this server and one that's not having the problem, just to eliminate
> the corrupted-binary theory.
>
>
>
The return is the same for the two servers,
$ sha1sum /usr/pgsql-9.6/bin/postmaster
56bcb4d644a8b00f07e9bd42f9a3f02
>
> That would result in nonsensical gdb output, most likely; but Glauco's
> trace is internally consistent enough that I doubt gdb is lying to us.
> In any case, the crash is an observable fact :-(
>
>
> The system is a CentOS 7, and PG was installed using PGDG's YUM repository.
We are pretty sur
last_lockfile_recheck_time = 1515438348
last_touch_time = 1515438348
__func__ = "ServerLoop"
#15 0x00675b69 in PostmasterMain (argc=argc@entry=3,
argv=argv@entry=0x27ca210)
at postmaster.c:1327
opt =
status =
userDoption =
listen_addr_saved =
i =
output_config_variable =
__func__ = "PostmasterMain"
#16 0x0047053e in main (argc=3, argv=0x27ca210) at main.c:228
Kind Regards,
Glauco Torres
