This sounds like it might be a duplicate of bug #12465: http://www.postgresql.org/message-id/20150108212429.11502.18220@wrigleys.postgresql.org
.m