On 11/10/2014 10:59 AM, Jeff Janes wrote:
> On Mon, Nov 10, 2014 at 10:48 AM, Josh Berkus <josh@agliodbs.com> wrote:
>
>> On 12/31/2013 09:55 AM, Tom Lane wrote:
>>> Josh Berkus <josh@agliodbs.com> writes:
>>>> Tom,
>>>>> There's an abbreviated version of this argument in the comments in
>>>>> my proposed patch at
>>>>> http://www.postgresql.org/message-id/11927.1384199294@sss.pgh.pa.us
>>>>> What I'm hoping will happen next is that the complainants will
>> hot-patch
>>>>> that and see if it fixes their problems. We can't really determine
>>>>> what to do without that information.
>>>
>>>> Unfortunately, the original reporter of this issue will not be available
>>>> for testing for 2-3 weeks, and I haven't been able to devise a synthetic
>>>> test which clearly shows the issue.
>>>
>>> Ping? I've been waiting on committing that patch pending some real-world
>>> testing. It'd be nice to resolve this question before we ship 9.3.3,
>>> which I'm supposing will be sometime in January ...
>>
>> Did this patch every make it in? Or did it hang waiting for verification?
>>
>
> It made it in:
>
> commit 4162a55c77cbb54acb4ac442ef3565b813b9d07a
> Author: Tom Lane <tgl@sss.pgh.pa.us>
> Date: Tue Feb 25 16:04:09 2014 -0500
Thanks, then the problem I'm seeing now is something else.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com