Re: BUG #14295: Hot standby crash during tsvector rebuild

Hi Tom,
This a 64 bit machine and I’m happy to provide remote access if that helps. Requested info below. Thanks for the follow up!

$ uname -a
SunOS pg-test-1.wtsky.net 5.11 11.3 sun4v sparc SUNW,T5240 Solaris

$ pg_config
BINDIR = /usr/postgresql/9.4/bin
DOCDIR = /usr/share/doc/postgresql-doc-9.4
HTMLDIR = /usr/share/doc/postgresql-doc-9.4
INCLUDEDIR = /usr/include/postgresql
PKGINCLUDEDIR = /usr/include/postgresql
INCLUDEDIR-SERVER = /usr/include/postgresql/server
LIBDIR = /usr/lib/sparcv9
PKGLIBDIR = /usr/lib/sparcv9/postgresql
LOCALEDIR = /usr/share/locale
MANDIR = /usr/share/postgresql/9.4/man
SHAREDIR = /usr/share/postgresql/9.4
SYSCONFDIR = /etc/postgresql/9.4
PGXS = /usr/lib/sparcv9/postgresql/pgxs/src/makefiles/pgxs.mk
CONFIGURE = 'CC=/opt/solarisstudio12.4/bin/cc' 'CFLAGS=-m64 -xO5 -fast -fsimple=0 -xalias_level=any' 'LDFLAGS=-m64' '--with-libedit-preferred' '--with-pam' '--with-openssl' '--with-libxml' '--with-libxslt' '--mandir=/usr/share/postgresql/9.4/man' '--docdir=/usr/share/doc/postgresql-doc-9.4' '--sysconfdir=/etc/postgresql/9.4' '--datarootdir=/usr/share/' '--datadir=/usr/share/postgresql/9.4' '--bindir=/usr/postgresql/9.4/bin' '--libdir=/usr/lib/sparcv9/' '--libexecdir=/usr/lib/postgresql/' '--includedir=/usr/include/postgresql/' '--enable-dtrace' 'DTRACEFLAGS=-64' '--enable-nls' '--enable-integer-datetimes' '--enable-thread-safety' '--disable-rpath' '--with-uuid=e2fs' '--with-pgport=5432' '--with-system-tzdata=/usr/share/lib/zoneinfo'
CC = /opt/solarisstudio12.4/bin/cc -Xa
CPPFLAGS = -I/usr/include/libxml2
CFLAGS = -m64 -xO5 -fast -fsimple=0 -xalias_level=any
CFLAGS_SL = -KPIC
LDFLAGS = -L../../../src/common -m64 -Wl,--as-needed
LDFLAGS_EX =
LDFLAGS_SL =
LIBS = -lpgcommon -lpgport -lxslt -lxml2 -lpam -lssl -lcrypto -lz -ledit -lnsl -lsocket -lm
VERSION = PostgreSQL 9.4.8

> On Sep 2, 2016, at 6:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Spencer Thomason <spencer(at)whiteskycommunications(dot)com> writes:
>> I have included the master and slave configs and python scripts that trigger this on our systems.
>
> Thanks for sending this. Unfortunately I've had zero success reproducing
> the problem so far. I had about run out of ideas as to what might explain
> why it fails for you and not me, when I noticed this:
>
>> Also, I should note that this is on a SPARC T2 at 1.4GHz so the single thread performance might be a factor as well.
>
> Am I right in thinking that is a 32-bit machine? That might have
> something to do with it (notably because of different maxalign).
> Is the production machine you originally saw the problem on also 32-bit?
>
> While I'm asking questions, could you send along the output of pg_config
> for the build you're using?
>
> regards, tom lane