On Mon, Jan 26, 2015 at 2:19 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> You should definitely also update to 9.3.5 (or next week, 9.3.6) ASAP.
> Even if this specific problem isn't fixed, there's a bunch of things
> that *are* fixed and will eventually bite you. 9.3.X has not been
> one of our most stable release branches :-(
I didn't consider the bug report in detail, but I think it's likely
that this was in fact the bug fixed by
6bfa88acd3df830a5f7e8677c13512b1b50ae813.
--
Peter Geoghegan