Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cilDx-00066l-9G for pgsql-sql@arkaria.postgresql.org; Tue, 28 Feb 2017 17:06: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 1cilDw-0005LM-NU for pgsql-sql@arkaria.postgresql.org; Tue, 28 Feb 2017 17:06: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_2) (envelope-from ) id 1cilBs-0001g8-S5 for pgsql-sql@postgresql.org; Tue, 28 Feb 2017 17:03:57 +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 1cilBq-0007mY-J7 for pgsql-sql@postgresql.org; Tue, 28 Feb 2017 17:03:55 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id BD01D204D2; Tue, 28 Feb 2017 12:03:53 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 28 Feb 2017 12:03:53 -0500 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-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=VT310T89l5Iv5hi 19R/eLRHSW5c=; b=aOuw2rxuPv50ODmSWCXeagxQBI5SwrNdJLsh1G0FDjb4yir oiJnqsa+WryHG06qotUVDql9a1bwv0w7rhvwhjlcyBeNeEjaA19o+/MUdEtkxgzk T81XQEPj4zXsFq+pb5Q8yEDweis59EIk3yChXNKpTMVcaEpZviHqi89grtBQ= 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-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=VT310T89l5Iv5hi19R/eLRHSW5c=; b=e1n35/s7J+zmes1JdL3w CVrF6riAJUp73iPKeFi3tlX/IIDE84RCmCueNo3ZO27TV30BtnQp6iDjylAIz6/d sF+R1HfGWvkdUvLzAy6jlWfxh6iI/mijfE2/CdtlgjW54gfrjtrVXoPAK0cfUHhk lH+yf16qy+n6BwDknWpqJZk= X-ME-Sender: X-Sasl-enc: Bma7y77sn2xZbs6BnT25Bg1tSQMrGHHk92XxOs4M+GzZ 1488301433 Received: from [192.168.1.2] (174-21-203-58.tukw.qwest.net [174.21.203.58]) by mail.messagingengine.com (Postfix) with ESMTPA id 49F552423E; Tue, 28 Feb 2017 12:03:53 -0500 (EST) Subject: Re: FDW Process ID (PID) To: Gaurav Tomar , pgsql-sql@postgresql.org References: From: Adrian Klaver Message-ID: <512979e5-5997-ca44-05a4-41e9d1a9ca4b@aklaver.com> Date: Tue, 28 Feb 2017 09:03:52 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 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/27/2017 10:35 PM, Gaurav Tomar wrote: > Hi, > > While using the FDW we connect one database to another database and > access the remote data. > while connecting the other database can i pass the process id (PID) to FDW. Which pid? And what do you want to do with it? > > Regards, > > Gaurav > > +91 876 265 4621 > -- 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