Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aT1OC-0003cm-CW for pgsql-sql@arkaria.postgresql.org; Tue, 09 Feb 2016 06:03:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aT1OB-0000xY-VV for pgsql-sql@arkaria.postgresql.org; Tue, 09 Feb 2016 06:03:04 +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) (envelope-from ) id 1aT1OA-0000xC-NX for pgsql-sql@postgresql.org; Tue, 09 Feb 2016 06:03:03 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aT1O8-00089m-AY for pgsql-sql@postgresql.org; Tue, 09 Feb 2016 06:03:01 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id E795E203DD for ; Tue, 9 Feb 2016 01:02:58 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 09 Feb 2016 01:02:58 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=quK/Ws30TI7jZHKD1Zt4384QPKo=; b=WT8/AV fa7P65V9L9qVr9+IOX+x96M6GPkjQwLQn4uhK1CBwjjWqkdXPWGpm4WLXvpYrEfU s9Xauhi5Pi1p7a/giww6b0QS6gXBIFQf3tKkzWGBLRBSUGVyufTE6r/UkB0YPRRg w7WTyWJ6W6vPQ1oxVpN3Qg3K9O0F5bnY80Wrc= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=quK/Ws30TI7jZHK D1Zt4384QPKo=; b=cgXE3f+c2GYWSh5ACXIEVQNplvabJH3Ygz6Zj4EXcUVDZBs bPPoYfTq5Jrb1PIpi3u9zflqEvOY/R52GTvfUqyKKk0Hpton2ElvRUJ23i/8lP6S cPpcWijuR9p+PnETBS/u+Dcb4qzXGM7/tjjONpS3W0RQMvcrL+88GW+D2ErY= X-Sasl-enc: NY+jOh3bVZZtdCMpIt2GE8oiPczxY1hpYPeJQqCfJSbK 1454997778 Received: from [192.168.1.2] (174-21-70-246.tukw.qwest.net [174.21.70.246]) by mail.messagingengine.com (Postfix) with ESMTPA id 3322C6800E8; Tue, 9 Feb 2016 01:02:58 -0500 (EST) Subject: Re: Question on PostgreSQL DB behavior w.r.t JOIN and sort order. To: "Venkatesan, Sekhar" , "David G. Johnston" References: <21082.1454994009@sss.pgh.pa.us> Cc: Tom Lane , "pgsql-sql@postgresql.org" From: Adrian Klaver Message-ID: <56B980D1.7010509@aklaver.com> Date: Mon, 8 Feb 2016 22:01:53 -0800 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) 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 02/08/2016 09:53 PM, Venkatesan, Sekhar wrote: > Yes. is there an option/configuration to tell the postgres > optimizer/planner to generate plans to include the sort order instead of > speed? What columns in a table would that be and then what order? > > *From:*David G. Johnston [mailto:david.g.johnston@gmail.com] > *Sent:* Tuesday, February 09, 2016 11:20 AM > *To:* Venkatesan, Sekhar > *Cc:* Tom Lane; pgsql-sql@postgresql.org > *Subject:* Re: [SQL] Question on PostgreSQL DB behavior w.r.t JOIN and > sort order. > > On Monday, February 8, 2016, Venkatesan, Sekhar > > wrote: > > Is there a way to tell the optimizer to retain the sort order if that is > possible please? > > You mean, besides the ORDER BY clause? > > David J. > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql