Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fRmRo-0000Hg-TS for pgsql-admin@arkaria.postgresql.org; Sat, 09 Jun 2018 22:35:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fRmRm-0001VP-NP for pgsql-admin@arkaria.postgresql.org; Sat, 09 Jun 2018 22:34:58 +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.89) (envelope-from ) id 1fRmRk-0001UA-QE for pgsql-admin@lists.postgresql.org; Sat, 09 Jun 2018 22:34:58 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fRmRg-0006xw-PE for pgsql-admin@postgresql.org; Sat, 09 Jun 2018 22:34:55 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A3EDB21448; Sat, 9 Jun 2018 18:34:51 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sat, 09 Jun 2018 18:34:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; 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; s=fm3; bh=ib0nZU5goX1M634U4r0bCskaErYN6 qQlWEZOsLbq1Z8=; b=02bxaEayO3LDiPF16f2tAU6u9u5L+S1NuQAYlRHor2jwe IRxb7lUTNopDGPcQovQM+TXy+fk99X12g7E/JkzxJhpbD12MCm9nAVOxGtRAEMgM SjhGLcLI2eX1MCeZMsQOhQ0GMXMSxD/XYfj+haiyZLejpwlcLYAztAqEzeKQYW0b yYRNU5XWgXt3R5WN70a/Yqm/2wQGhSR4NJOvcZEBGgkUtPLx6IEVm/XwhJ/n1v/z gx7cnzUwLwsQA0yKRAQxss305E7bh2GnsjN2ee5MssN963Wh4eVXedgEt95CNFk0 EOl2+PWUs+/qldKIGV+V0Jg1toAaXWqvVeD/K+/Ow== DKIM-Signature: v=1; a=rsa-sha256; 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; s=fm2; bh=ib0nZU 5goX1M634U4r0bCskaErYN6qQlWEZOsLbq1Z8=; b=RzmaOMFqroVVncVfkB3zvA 7izzDaRn2cJTfFdYXMIqn1EAV78BSDPCFWNzcwcO/f+28LpRu573tFf92UuVeeGt L7GdzvLdRxVKPmsl/bYtMGmGxJK0Hqfe8IEMFy7vM7pzv2xT9RlirUSrflfiVKFA ex34Nn58fx+wgxsooO25ivVJoYqZHaJNh6YIxdSUx6kQid7B8RRY2RSo+6vx+lYl OQrJkUySeRN2/Kyz2/TRXQH7l8wm23QGfzcrdpjkNpR4KLYCe40t54A8klfrZETp 7WGrVydFfFUhPBMx5je/T8J4xjV+i1fVA3wLSEjWJU7kZJwKm5Z/VpxsY+OJtmcA == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from [192.168.1.3] (unknown [71.212.159.209]) by mail.messagingengine.com (Postfix) with ESMTPA id AFDCE10255; Sat, 9 Jun 2018 18:34:50 -0400 (EDT) Subject: Re: Fwd: compressed bits in sql table To: SANDEEP GOURNENI , pgsql-admin@lists.postgresql.org, pgsql-general@lists.postgresql.org, pgsql-admin@postgresql.org References: From: Adrian Klaver Message-ID: <52af8d9e-e6bf-9db7-ee4c-29beaaab28ec@aklaver.com> Date: Sat, 9 Jun 2018 15:34:49 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 06/09/2018 02:40 PM, SANDEEP GOURNENI wrote: > > Hi all, > > How can we read compressed bits in postgres.In one of my table field  i > have compressed bits.how to read and write them in postgres using cobol > program. You are going to need to be more specific: 1) What version of Postgres? 2) What is the field type? 3) Are you referring to the TOAST table? > > Thanks, > Sandeep > -- Adrian Klaver adrian.klaver@aklaver.com