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 1fRnJ3-0004QE-9B for pgsql-admin@arkaria.postgresql.org; Sat, 09 Jun 2018 23:30: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 1fRnJ2-0006B1-7G for pgsql-admin@arkaria.postgresql.org; Sat, 09 Jun 2018 23:30:00 +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 1fRnJ1-0006As-Q4 for pgsql-admin@lists.postgresql.org; Sat, 09 Jun 2018 23:30:00 +0000 Received: from mail-ot0-x241.google.com ([2607:f8b0:4003:c0f::241]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fRnIz-0008B4-3v for pgsql-admin@lists.postgresql.org; Sat, 09 Jun 2018 23:29:58 +0000 Received: by mail-ot0-x241.google.com with SMTP id q17-v6so19820896otg.2 for ; Sat, 09 Jun 2018 16:29:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=6R+R/r7BPkjHGDNdok7b6bQAhTPJkO2jUA5YuSUIMh4=; b=KXFBmWMgQTijT+7IuGgfQ7WcTX4v/iSjG54nKfD3eHR2c4S9xDvGM4yM3QiD4V6ach KPI7hTP0LtAbt3RKn4+PV1ZxYiMsOBAdtGgACmcoX0eYn3k+YCkYMS0G1Y27ToNKrSF7 piGjJ+2oWROj017VXKNxnri2g8oHH6ynszdD2XYAPU1NkrZ6O1/IrF5UM4RfVHOq7Nw1 qQidK27k9PJ9xpZTh7VuQbFiobsYIFZKC1D4bykz7bxL1zKOKa7B8VLYG8OPBIwfclFM C9+5rSxM03wh/hIsZm8wLFVu0X/pspnUKLLcef/mpzE+z8OTNHwSkMmLzad/+sihX6vt hlMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=6R+R/r7BPkjHGDNdok7b6bQAhTPJkO2jUA5YuSUIMh4=; b=YrUz07epHBMk8O9xsmwZEti7fYqYZ03cutVv03SgemDTJNwNmn4Q5w6cdk6refShNh Mc+/dRl4B8HzlENC8aK0/Hj80iCc0ryGAEgYDwuGnISsjim7vxQgnnHX/iWvMxEt0wR/ kEdMOPa5dhcaAvEK4sQ+yYAFDyv7Nz1RGQYP7YgkoDrBiTK0dIzEGrXNBSxU3ofHDvDb nV0xpVru0HwE6uzDbw1V9MxrJ8X8fQN/v8Bh8j+tvp4FoiMs/DDCQWeHnZOUOmirD/dp 0h+NK8iQ7ZbYiGcvhho6yDpyAITMjSlJOoBuez5bPE+ARmVpUq4NskCzVnC3gxtfbaYD itOg== X-Gm-Message-State: APt69E2m39DT+C/abX9eO6OBvAgghN9qVjvunHUxCd0xw4iCudhwJ6Ci WuaeetaWe5jIo+crm6lJd6zd8Q== X-Google-Smtp-Source: ADUXVKIg156kfedX3RJXKPrRTZiuQ/MNTOQIONIThKv+hLVST57KcoSL6s7YZtZtsl7LHuJTpyHDFQ== X-Received: by 2002:a9d:5b49:: with SMTP id e9-v6mr7375112otj.193.1528586996082; Sat, 09 Jun 2018 16:29:56 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id m17-v6sm10679306otk.1.2018.06.09.16.29.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 09 Jun 2018 16:29:55 -0700 (PDT) Subject: Re: Fwd: compressed bits in sql table To: pgsql-admin@lists.postgresql.org References: <52af8d9e-e6bf-9db7-ee4c-29beaaab28ec@aklaver.com> From: Ron Message-ID: Date: Sat, 9 Jun 2018 18:29:54 -0500 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: multipart/alternative; boundary="------------619658734BA450A0DC8A73C3" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------619658734BA450A0DC8A73C3 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Are you asking how to SELECT ... WHERE based on individual bits in this CHAR(32) field? How were the bits encoded in the first place? On 06/09/2018 05:43 PM, SANDEEP GOURNENI wrote: > Postgres version is 10.4 > field type is char(32).basically its a fee bit field. > it is related to my application. > > thanks, > Sandeep > > On Sun, Jun 10, 2018 at 4:04 AM Adrian Klaver > wrote: > > 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? > -- Angular momentum makes the world go 'round. --------------619658734BA450A0DC8A73C3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Are you asking how to SELECT ... WHERE based on individual bits in this CHAR(32) field? 

How were the bits encoded in the first place?

On 06/09/2018 05:43 PM, SANDEEP GOURNENI wrote:
Postgres version is 10.4
field type is char(32).basically its a fee bit field.
it is related to my application.

thanks,
Sandeep

On Sun, Jun 10, 2018 at 4:04 AM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
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?

--
Angular momentum makes the world go 'round.
--------------619658734BA450A0DC8A73C3--