On December 22, 2017 7:52:54 PM GMT+01:00, Tom Lane wrote:
>Andres Freund writes:
>> On 2017-12-22 11:00:54 -0500, Tom Lane wrote:
>>> I do not think it is reasonable for these functions to not set the
>>> output variable at all in the overflow case; it is not their job
>>> to opine on whether
Andres Freund writes:
> On 2017-12-22 11:00:54 -0500, Tom Lane wrote:
>> I do not think it is reasonable for these functions to not set the
>> output variable at all in the overflow case; it is not their job
>> to opine on whether the caller may use the result.
> I don't agree. Please note that t
Hi,
On 2017-12-22 11:00:54 -0500, Tom Lane wrote:
> Andres Freund writes:
> > Use new overflow aware integer operations.
>
> I just tried to compile manually on prairiedog for the first time since
> this went in, and noticed that it now produces a boatload of warnings
> like
>
> int.c: In funct
Disallow UNION/INTERSECT/EXCEPT over no columns.
Since 9.4, we've allowed the syntax "select union select" and variants
of that. However, the planner wasn't expecting a no-column set operation
and ended up treating the set operation as if it were UNION ALL.
Pre-v10, there seem to be some executo
Disallow UNION/INTERSECT/EXCEPT over no columns.
Since 9.4, we've allowed the syntax "select union select" and variants
of that. However, the planner wasn't expecting a no-column set operation
and ended up treating the set operation as if it were UNION ALL.
Pre-v10, there seem to be some executo
Fix UNION/INTERSECT/EXCEPT over no columns.
Since 9.4, we've allowed the syntax "select union select" and variants
of that. However, the planner wasn't expecting a no-column set operation
and ended up treating the set operation as if it were UNION ALL.
Turns out it's trivial to fix in v10 and la
Disallow UNION/INTERSECT/EXCEPT over no columns.
Since 9.4, we've allowed the syntax "select union select" and variants
of that. However, the planner wasn't expecting a no-column set operation
and ended up treating the set operation as if it were UNION ALL.
Pre-v10, there seem to be some executo
Fix UNION/INTERSECT/EXCEPT over no columns.
Since 9.4, we've allowed the syntax "select union select" and variants
of that. However, the planner wasn't expecting a no-column set operation
and ended up treating the set operation as if it were UNION ALL.
Turns out it's trivial to fix in v10 and la
Andres Freund writes:
> Use new overflow aware integer operations.
I just tried to compile manually on prairiedog for the first time since
this went in, and noticed that it now produces a boatload of warnings
like
int.c: In function 'int2pl':
int.c:735: warning: 'result' may be used uninitialize
Add optional compression method to SP-GiST
Patch allows to have different types of column and value stored in leaf tuples
of SP-GiST. The main application of feature is to transform complex column type
to simple indexed type or for truncating too long value, transformation could
be lossy. Simple
Hi,
On 2017-12-22 21:16:10 +1300, Thomas Munro wrote:
> Andres, your machine francolin crashed -- got a core file?
Unfortunately not - it appears the buildfarm cleared it away :(
Might try to reproduce it on that machine...
Greetings,
Andres Freund
On Fri, Dec 22, 2017 at 1:48 AM, Thomas Munro
wrote:
> I don't think that's quite it, because it should never have set
> 'writing' for any batch number >= nbatch.
>
> It's late here, but I'll take this up tomorrow and either find a fix
> or figure out how to avoid antisocial noise levels on the bu
12 matches
Mail list logo
