Re: Abbreviated keys for Numeric

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
Subject: Re: Abbreviated keys for Numeric
Date: 2015-03-25 22:26:27
Message-ID: 87619p568e.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Peter" == Peter Geoghegan <pg(at)heroku(dot)com> writes:

Peter> You still pointlessly check memtupcount here:

Peter> + if (memtupcount < 10000 || nss->input_count < 10000 || !nss->estimating)
Peter> + return false;

It's in a register; the test is free.

Peter> This cast to void is unnecessary:

Peter> + (void) ssup;

It's an explicit statement that the parameter is otherwise unused.
Maybe that compiler warning isn't usually on by default, but I
personally regard it as good style to be explicit about it.

Peter> Please try and at least consider my feedback. I don't expect you
Peter> to do exactly what I ask, but I also don't expect you to
Peter> blithely ignore it.

You should really stop digging this hole deeper.

>> The INT64_MIN/MAX changes should be committed fairly soon. (I
>> haven't posted a patch for TRACE_SORT)

Peter> I wouldn't assume that.

Oh ye of little faith. I would not have said that had I not already been
informed of it by a committer, and indeed it is now committed.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-03-25 22:48:57 Re: Remove fsync ON/OFF as a visible option?
Previous Message Andres Freund 2015-03-25 21:49:21 pgsql: Centralize definition of integer limits.