Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-sql-owner+M39088=pgsql+2Dsql=arkaria.postgresql.org@postgresql.org>)
	id 1d6a2e-0004Uj-Hp
	for pgsql-sql@arkaria.postgresql.org; Fri, 05 May 2017 10:00:52 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-sql-owner+M39088=pgsql+2Dsql=arkaria.postgresql.org@postgresql.org>)
	id 1d6a2d-000566-TB
	for pgsql-sql@arkaria.postgresql.org; Fri, 05 May 2017 10:00:51 +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 <depesz@depesz.com>)
	id 1d6a2d-00055u-EQ
	for pgsql-sql@postgresql.org; Fri, 05 May 2017 10:00:51 +0000
Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com)
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.84_2)
	(envelope-from <depesz@depesz.com>)
	id 1d6a2R-0006jb-V1
	for pgsql-sql@postgresql.org; Fri, 05 May 2017 10:00:50 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com;
 s=20170201;
	h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To:Message-ID:Subject:Cc:To:Sender:From:Date;
 bh=EoxgEt3bPoDBn0twIAOzO8wMGE/gnqkIrwojIrqgu88=;
	b=M8/2V0irNJzqCQL6lPQo3Alnsd2Nr+4W+4wnDyx3ElV55udadwV8Brt0enWi2xMoseIS8KfCMUVSle63RGpM782XnuPSE4dD9sTD9gVSYNq2rH2Y70iZxk4mHCjdPDKxWlaAoeESPwpate5mAiDExE0yp7y0gKUJK8JQR61/IGI=;
Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com)
	by depesz.com with esmtpa (Exim 4.84_2)
	(envelope-from <depesz@depesz.com>)
	id 1d6a2P-0006Yp-Au; Fri, 05 May 2017 12:00:37 +0200
Date: Fri, 5 May 2017 12:00:37 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
To: Gary Stainburn <gary.stainburn@ringways.co.uk>
Cc: pgsql-sql@postgresql.org
Subject: Re: Most recent row
Message-ID: <20170505100037.GA23734@depesz.com>
Reply-To: depesz@depesz.com
References: <201705050925.04194.gary.stainburn@ringways.co.uk>
 <20170505093505.GA5611@depesz.com>
 <201705051044.54259.gary.stainburn@ringways.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <201705051044.54259.gary.stainburn@ringways.co.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-sql>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-sql.postgresql.org>
List-Owner: <mailto:pgsql-sql-owner@postgresql.org>
List-Post: <mailto:pgsql-sql@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-sql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
X-Mailing-List: pgsql-sql
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

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



-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql