Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1al2sx-0006g6-8J for pgsql-sql@arkaria.postgresql.org; Tue, 29 Mar 2016 23:17:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1al2sw-00031U-05 for pgsql-sql@arkaria.postgresql.org; Tue, 29 Mar 2016 23:17:18 +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 1al2rx-0001vy-1k for pgsql-sql@postgresql.org; Tue, 29 Mar 2016 23:16:17 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1al2rt-0006cg-Tc for pgsql-sql@postgresql.org; Tue, 29 Mar 2016 23:16:15 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 01D8C21B79 for ; Tue, 29 Mar 2016 19:16:11 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Tue, 29 Mar 2016 19:16:12 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= 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=Ovr9TdJInapqaTIEWfIlf8y2Uek=; b=KjdBND Q9pJjcsB40TYuZYYLWJQkVL1Y2BtZ/Wg/fpjpX+f5a29d2F8KzkWlHwLkpS8pgNa wTPZXOLExqKfiIqpriwEbYEY+bkzb63jcgMLSf8vhyyxc5eBQfTjjO/+Vqzujxl1 BtnXSbDOhXHafJwOkb/ZnhRu6hNFn43HDwxOo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=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=Ovr9TdJInapqaTI EWfIlf8y2Uek=; b=GPWvzK7EVFbS6aFp9xtgpllVg7QJe6lCPiHy76gRBTCzNgs NX0hb4hnyExOKVNzQFCqrMV/TjQDRfC8wD6S5AK36cLOwT9pebRqK+NOBLUt8fS1 rDljfFH/6y1HjzqZhbS6E+r0VspHKLwqouxLf9nSfS64JSLkQd8SxFdarvRU= X-Sasl-enc: 6hGH78UVGctjNP3Z9ZTYrIeMFN4WVos9E839E1yuUx+k 1459293371 Received: from [192.168.1.2] (174-24-160-10.tukw.qwest.net [174.24.160.10]) by mail.messagingengine.com (Postfix) with ESMTPA id 75F74C00016; Tue, 29 Mar 2016 19:16:11 -0400 (EDT) Subject: Re: how plsql work on postgresql To: Selina Tech , pgsql-sql@postgresql.org References: From: Adrian Klaver Message-ID: <56FB0CBA.8010804@aklaver.com> Date: Tue, 29 Mar 2016 16:16:10 -0700 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.7.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 03/29/2016 03:57 PM, Selina Tech wrote: > Hi, All > > I just start to learn plsql and plpgsql. There are a lot of > comparison of pl/sql and pl/pgsql available online. I am wondering why > plsql work well on Postgresql and how it work? Is the code converted to > plpgsql code? > If use postgresql database server, which one is better > between plsql and pl/pgsql? I find myself using pl/pgsql more then plsql(assuming you mean this(http://www.postgresql.org/docs/9.5/interactive/xfunc-sql.html)) just because pl/pgsql offers more ways to manipulate data. FYI, there are languages available e.g. pl/pythonu, pl/perl, pl/tcl. pl/java, etc. Some resources: http://www.postgresql.org/docs/9.5/interactive/plpgsql-porting.html http://ora2pg.darold.net/documentation.html#plsql_to_plpsql_convertion > > > Your feedback is highly appreciated. > > Sincerely, > Selina -- 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