Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d6at7-0007T7-Dh for pgsql-sql@arkaria.postgresql.org; Fri, 05 May 2017 10:55:05 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d6at7-0003vp-0N for pgsql-sql@arkaria.postgresql.org; Fri, 05 May 2017 10:55:05 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d6at6-0003uw-59 for pgsql-sql@postgresql.org; Fri, 05 May 2017 10:55:04 +0000 Received: from hub.ringways.co.uk ([88.211.105.30] helo=ringways.co.uk) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d6asz-0007fw-FX for pgsql-sql@postgresql.org; Fri, 05 May 2017 10:55:03 +0000 Received: from eddie.ringways.co.uk ([10.1.1.115]) by ringways.co.uk with esmtp (Exim 4.89) (envelope-from ) id 1d6asx-000Pit-2Z for pgsql-sql@postgresql.org; Fri, 05 May 2017 11:54:55 +0100 From: Gary Stainburn Organization: Ringways Garages Ltd To: pgsql-sql@postgresql.org Subject: Re: Most recent row Date: Fri, 5 May 2017 11:54:54 +0100 User-Agent: KMail/1.9.10 References: <201705050925.04194.gary.stainburn@ringways.co.uk> <201705051044.54259.gary.stainburn@ringways.co.uk> <20170505100037.GA23734@depesz.com> In-Reply-To: <20170505100037.GA23734@depesz.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201705051154.54863.gary.stainburn@ringways.co.uk> X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 112282 [May 05 2017] X-KLMS-AntiSpam-Version: 5.7.0.14 X-KLMS-AntiSpam-Envelope-From: gary.stainburn@ringways.co.uk X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Info: LuaCore: 219 219 5c25d3d119ea48db9a5032001f8be732dc5ace77, {msgid_created_by_recepient}, 127.0.0.200:5.2.1;ringways.co.uk:7.1.1;eddie.ringways.co.uk:7.1.1;127.0.0.199:7.1.2,5.2.1;d41d8cd98f00b204e9800998ecf8427e.com:7.1.1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2017/05/04 14:05:37 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2017/05/05 05:04:00 #9490597 X-KLMS-AntiVirus-Status: Clean, skipped X-Spam-Score: -50.8 (--------------------------------------------------) X-Spam-Report: Spam detection software, running on the system "ollie2.ringways.co.uk", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see Gary Stainburn for details. Content preview: On Friday 05 May 2017 11:00:37 hubert depesz lubaczewski wrote: > On Fri, May 05, 2017 at 10:44:54AM +0100, Gary Stainburn wrote: > > > How many rows are in people? How many in assessments? Do you really > > > want data on all people? Or just some? > > > > I was looking for a balanced solution, combining performance and SQL > > 'purity'. > > Solution depends on answers to questions I asked. Will you always get > data for all people? Or just some? How many assessments per person will > there usually be? > > Best regards, > > depesz [...] Content analysis details: (-50.8 points, 15.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -50 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.1 SCORE_RCPTS Adding score for each recipient -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 1.0 RING_SAFE No description available. X-forward-disable: yes X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org On Friday 05 May 2017 11:00:37 hubert depesz lubaczewski wrote: > On Fri, May 05, 2017 at 10:44:54AM +0100, Gary Stainburn wrote: > > > How many rows are in people? How many in assessments? Do you really > > > want data on all people? Or just some? > > > > I was looking for a balanced solution, combining performance and SQL > > 'purity'. > > Solution depends on answers to questions I asked. Will you always get > data for all people? Or just some? How many assessments per person will > there usually be? > > Best regards, > > depesz Oddly, part of my reply was missing. As I said, there are currently 720 rows in the people table. The will be a new assessment record for each person roughly every six months. The dataset will be open ended so will slowly but indefinitely grow. The part that was missing was that there will be new people records added who initially will not have an assessment. They will still need to be included in the report. -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql