Re: Bug in tables column data in postgres database

As others have said, it is nearly impossible for postgres to be usable in
any environment with the bug you reported, and yet it is. It is 99.9999 %
likely the bug is somewhere else. You have provided no reproduction steps
as well, so no action could even be taken if it were an issue. This is not
a customer support channel with Salad as well. If you wish to have that
type of support, you may wish to contact one of the many companies that
provide support for postgresql.

On Fri, Mar 4, 2022, 9:17 AM Sarita Sharma <saritakumarisharma61(at)gmail(dot)com>
wrote:

> Hello Team,
> 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.
> The toggling issue I told , I have analysed it many times and I only
> correcting data whenever my data got toggle like I have already explained.
> If you find it a genuine issue , you can take it under consideration.
> As a employee I have already informed this issue to my senior colleague.
>
> Thanks and Regards,
> Sarita
>
> On Fri, 4 Mar 2022, 01:33 Steve Midgley, <science(at)misuse(dot)org> wrote:
>
>>
>>
>> On Thu, Mar 3, 2022 at 11:27 AM David G. Johnston <
>> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>>
>>> On Thu, Mar 3, 2022 at 12:13 PM Sarita Sharma <
>>> saritakumarisharma61(at)gmail(dot)com> wrote:
>>>
>>>> I am working as a Java developer and for backend database I am using
>>>> postgres database. I am generating this tables using entity classes of Java
>>>> and Jpa configuration to handling database connectivity and table creation.
>>>> I am finding this toggling issue on my day to day work activity . I am
>>>> still working with same situation. And I only have to correct data whenever
>>>> its value keeps changing automatically.
>>>> Please take my concern .
>>>>
>>>>
>>> You are going to have to produce a self-contained example program (and
>>> database schema) that demonstrates the issue if you want to have any hope
>>> of having it solved. Once you've done that, figuring out which piece of
>>> software is "buggy" should become possible. Until you can manage that,
>>> handing off the problem to someone to solve is not going to work.
>>> David J.
>>>
>>
>> Ditto this point, and to say that in my experience with databases in
>> general and postgres specifically, I've never even heard of this type of
>> problem manifesting, or similar to like it.
>>
>> Whereas, I've personally encountered this type of unexpected "toggling"
>> of data in the ORM or other language-specific layers many, many times. So
>> just from a parsimony perspective, it's wise to look at and instrument your
>> java stack to find the problem: as it is almost certain that this type of
>> problem is in those layers. If it isn't there, it could be in some kind of
>> business logic code inside stored procedures in your postgres environment
>> of course -- that's also a very viable path of inquiry. But the idea that
>> postgres itself is toggling your data is so improbable, that you should
>> discount it in your analysis. It's more likely you have flaky ram or a
>> motherboard creating the issue (and those are also highly unlikely
>> candidates for this problem).
>> Steve
>>
>