Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cilFg-0006B0-5o for pgsql-sql@arkaria.postgresql.org; Tue, 28 Feb 2017 17:07:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cilFf-0001o9-IZ for pgsql-sql@arkaria.postgresql.org; Tue, 28 Feb 2017 17:07: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 ) id 1cilFd-0001gL-JA for pgsql-sql@postgresql.org; Tue, 28 Feb 2017 17:07:49 +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 1cilFb-0007sV-La for pgsql-sql@postgresql.org; Tue, 28 Feb 2017 17:07:48 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 003FF2090E; Tue, 28 Feb 2017 12:07:46 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 28 Feb 2017 12:07:46 -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=b8zKzhDi4RHDRDe NpBtEAMz2/Y0=; b=fB7FCI6XRmpGhMO3VXGSIciyN8QQ2oi5LM2ccvKW5Pk6eHU /KuYsAKIdepXVy9//PK8Ymume32T8ZEp2CpSxiyFF7e3jiqjFOBMOsp4gPkvQMza odcu8+C+adYy0q4iGQX+gDiVSH3l1ZxIrbw0uju5spIl29USLI0ncksk2HxE= 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=b8zKzhDi4RHDRDeNpBtEAMz2/Y0=; b=k6ZW7hqArBCDWtmxlS8p M1Rx89zFw+XdEJG1EcQ0p+DbJJwPRu6fxrXWYRWB2r30BUFaZIjxbyBLor+/p/n8 CQmE+WRdw55BfzdBz/v9M81s0Lx9i5K3pgNa9toqkKToWWRID61V0wekAwGuLskM hlWAOyDtgj3uQcY9UAZH9Uc= X-ME-Sender: X-Sasl-enc: XhpANJ48aCZ+4nkh5NwDkx4eEQEONAOQZvHWnMY1EbNl 1488301666 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 603BE24242; Tue, 28 Feb 2017 12:07:46 -0500 (EST) Subject: Re: FDW Process ID (PID) To: Gaurav Tomar , pgsql-sql@postgresql.org References: From: Adrian Klaver Message-ID: <327322c0-033b-0f2d-a48d-0502ea060a34@aklaver.com> Date: Tue, 28 Feb 2017 09:07:45 -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. Hmm, seems my first post ran a foul of some regex filter, so I will try again: What process are you trying to get the id from? What do you want to do with the process id? > > 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