From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Spencer Thomason <spencer(at)whiteskycommunications(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14295: Hot standby crash during tsvector rebuild |
Date: | 2016-09-02 23:46:35 |
Message-ID: | 921.1472859995@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Spencer Thomason | 2016-09-03 15:19:26 | Re: BUG #14295: Hot standby crash during tsvector rebuild |
Previous Message | Ed Kurowski | 2016-09-02 19:17:54 | Re: Full JSONb column returned over FDW when only single value needed |