On 10/28/16 8:23 AM, Merlin Moncure wrote:
On Thu, Oct 27, 2016 at 6:39 PM, Greg Stark <st...@mit.edu> wrote:
On Thu, Oct 27, 2016 at 9:53 PM, Merlin Moncure <mmonc...@gmail.com> wrote:
I think we can rule out faulty storage
Nobody ever expects the faulty storage
LOL
Believe me, I know. But the evidence points elsewhere in this case;
this is clearly application driven.
FWIW, just because it's triggered by specific application behavior
doesn't mean there isn't a storage bug. That's what makes data
corruption bugs such a joy to figure out.
BTW, if you haven't already, I would reset all your storage related
options and GUCs to safe defaults... plain old FSYNC, no cute journal /
FS / mount options, etc. Maybe this is related to the app, but the most
helpful thing right now is to find some kind of safe config so you can
start bisecting.
I would also consider alternatives to plsh, just to rule it out if
nothing else. I'd certainly look at some way to get sqsh out of the loop
(again, just to get something that doesn't crash). First idea that comes
to mind is a stand-alone shell script that watches a named pipe for a
filename; when it gets that file it runs it with sqsh and does something
to signal completion.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
