agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: Tom Lane <tgl@sss.pgh.pa.us>
To: Sarita Sharma <saritakumarisharma61@gmail.com>
Cc: Steve Midgley <science@misuse.org>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>
Cc: pgsql-sql <pgsql-sql@lists.postgresql.org>
Subject: Re: Bug in tables column data in postgres database
Date: Fri, 04 Mar 2022 09:43:22 -0500
Message-ID: <3849858.1646405002@sss.pgh.pa.us> (raw)
In-Reply-To: <CAOKMkZp=RjxGh+-LsuUNT07B4Rfz+C26cQknMMWcF8CdRJJgvg@mail.gmail.com>
References: <CAOKMkZoQ-7kqjLdJgkZxUGe8ODnF4ABhDL_42CvpdaRku7Uhbg@mail.gmail.com>
<MN2PR20MB27351176E5F01EB9655061BCBE049@MN2PR20MB2735.namprd20.prod.outlook.com>
<CAOKMkZoJzADk_Dr4LawY0K9Rm8iibWPYHPTwh2eDhxAbm9YfHA@mail.gmail.com>
<CAKFQuwZXWwcma2b=U7-+qseaiD6-z2Op+oKGMiV9EV0tRm=dGg@mail.gmail.com>
<CAJexoS+qi0uw=jT8vXueaHwfd2PF9kTbfXj9H2suH4kYdbnmcQ@mail.gmail.com>
<CAOKMkZp=RjxGh+-LsuUNT07B4Rfz+C26cQknMMWcF8CdRJJgvg@mail.gmail.com>
Sarita Sharma <saritakumarisharma61@gmail.com> writes:
> I am getting a genuine defect that from postgres database as I am working
> for a well recognised organization and I am only handling coding from
> layers that includes spring boot, Jpa configuration for database
> connectivity and postgres as database.
Look: you have not provided one single shred of evidence to demonstrate
that you are encountering a Postgres bug (as opposed to some other
problem). If you continue to repeat that claim without adding such
evidence, you're just wasting your time as well as the time of all the
readers of this mailing list.
There are some hints about formulating a well-documented problem
report here:
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
as well as in the fine manual:
https://www.postgresql.org/docs/current/bug-reporting.html
I will just mention one possible source of problems that might
perhaps match your issue, which is index corruption. If there's
recently been an OS update on the Postgres server's machine,
that becomes a lot more plausible as the cause:
https://wiki.postgresql.org/wiki/Locale_data_changes
But in any case, reindexing the indexes of the troublesome table(s)
would be a worthwhile step. If you still have problems after
that, you'll need to start localizing and documenting the trouble
as per the previous links. We cannot help you without a *lot*
more information than you've provided.
regards, tom lane
view thread (25+ messages) latest in thread
Message-ID: <3849858.1646405002@sss.pgh.pa.us>
Permalink: ../3849858.1646405002@sss.pgh.pa.us/
Also on: postgresql.org/message-id/3849858.1646405002@sss.pgh.pa.us
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, saritakumarisharma61@gmail.com, science@misuse.org, david.g.johnston@gmail.com, Jean-Marc.Voillequin@moodys.com, pgsql-sql@lists.postgresql.org
Subject: Re: Bug in tables column data in postgres database
In-Reply-To: <3849858.1646405002@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox