On Fri, Dec 7, 2012 at 1:14 PM, Magnus Hagander wrote:
> On Thu, Dec 6, 2012 at 6:39 PM, Dave Page wrote:
>> On Thu, Dec 6, 2012 at 11:48 AM, Magnus Hagander wrote:
>>> Certainly sounds like a very similar problem. If so, the query is
>>> simply buggy - it's just that a pg_upgrade'd environment
On Thu, Dec 6, 2012 at 6:39 PM, Dave Page wrote:
> On Thu, Dec 6, 2012 at 11:48 AM, Magnus Hagander wrote:
>> Certainly sounds like a very similar problem. If so, the query is
>> simply buggy - it's just that a pg_upgrade'd environment is *much*
>> more likely to run into the problem than before.
Thanks - I've committed and pushed the patch.
On Fri, Dec 7, 2012 at 10:39 AM, Per Wigren wrote:
> Unfortunately I don't have a build environment for this here at work but I
> can confirm that by manually applying the change to the query in
> edbPackage.cpp in the diff to the query I snatched fro
Unfortunately I don't have a build environment for this here at work but I
can confirm that by manually applying the change to the query in
edbPackage.cpp in the diff to the query I snatched from pg_log, the output
looks good. No more duplicates.
// Per
2012/12/6 Dave Page
> On Thu, Dec 6, 2012
On Thu, Dec 6, 2012 at 11:32 PM, Andrzej Zawadzki wrote:
> On 06.12.2012 18:39, Dave Page wrote:
>> On Thu, Dec 6, 2012 at 11:48 AM, Magnus Hagander wrote:
>>> Certainly sounds like a very similar problem. If so, the query is
>>> simply buggy - it's just that a pg_upgrade'd environment is *much*
