Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-sql-owner+archive@lists.postgresql.org>)
	id 1nPp7Z-0008Hq-UK
	for pgsql-sql@arkaria.postgresql.org; Thu, 03 Mar 2022 17:20:09 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-sql-owner+archive@lists.postgresql.org>)
	id 1nPp7Y-0004C6-S5
	for pgsql-sql@arkaria.postgresql.org; Thu, 03 Mar 2022 17:20:08 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <xof@thebuild.com>)
	id 1nPp7Y-0004Bt-Js
	for pgsql-sql@lists.postgresql.org; Thu, 03 Mar 2022 17:20:08 +0000
Received: from smtp67.iad3a.emailsrvr.com ([173.203.187.67])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <xof@thebuild.com>)
	id 1nPp7W-0005PP-9e
	for pgsql-sql@lists.postgresql.org; Thu, 03 Mar 2022 17:20:07 +0000
X-Auth-ID: xof@thebuild.com
Received: by smtp1.relay.iad3a.emailsrvr.com (Authenticated sender:
 xof-AT-thebuild.com) with ESMTPSA id B4698148D;
	Thu,  3 Mar 2022 12:20:03 -0500 (EST)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Subject: Re: Bug in tables column data in postgres database
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: 
 <CAOKMkZoQ-7kqjLdJgkZxUGe8ODnF4ABhDL_42CvpdaRku7Uhbg@mail.gmail.com>
Date: Thu, 3 Mar 2022 09:18:59 -0800
Cc: pgsql-sql@lists.postgresql.org
X-Mailbutler-Message-Id: E23AB508-4E71-4339-84A3-6DE99D75F72A
Content-Transfer-Encoding: quoted-printable
Message-Id: <39AFDD57-D4B2-4566-A78A-DE03351A60AD@thebuild.com>
References: 
 <CAOKMkZoQ-7kqjLdJgkZxUGe8ODnF4ABhDL_42CvpdaRku7Uhbg@mail.gmail.com>
To: Sarita Sharma <saritakumarisharma61@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-Classification-ID: eb1a0ad5-0251-4a75-b6da-febbbb6f78dc-1-1
List-Id: <pgsql-sql.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-sql@lists.postgresql.org>
List-Owner: <mailto:pgsql-sql-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-sql>
Archived-At: 
 <https://www.postgresql.org/message-id/39AFDD57-D4B2-4566-A78A-DE03351A60AD%40thebuild.com>
Precedence: bulk



> On Mar 3, 2022, at 08:45, Sarita Sharma =
<saritakumarisharma61@gmail.com> wrote:
>=20
>   Hi Team,
> I am a backend(server side) developer and I am using postgres database =
for storing my data to database. I have find a big challenge working =
with postgres database(version 13) as I have find  major issue working =
with  column in table of database as data keep toggling its value.=20
> eg::
> if I have stored data into table=20
> bike_table
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> bike_name    bike_prefix    bike_line
> V111               V                  111
> W222              W                 222
> X333               X                  333
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> if some other time if query is made for same table data might look =
like this
> bike_table
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> bike_name    bike_prefix    bike_line
> W111               V                  111
> X222              W                  222
> X333               X                  333
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> So usually bike_name  keep changing its name thats seems to me a =
toggling behaviour.
> Please take this issue as bug and work on this.


While never say never, the issue you are describing is essentially =
impossible.  Can we see the schema of the table, and the statements you =
are using to insert the data and query it?=