agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedBug in tables column data in postgres database
25+ messages / 13 participants
[nested] [flat]
* Bug in tables column data in postgres database
@ 2022-03-03 16:45 Sarita Sharma <saritakumarisharma61@gmail.com>
0 siblings, 4 replies; 25+ messages in thread
From: Sarita Sharma @ 2022-03-03 16:45 UTC (permalink / raw)
To: pgsql-sql@lists.postgresql.org
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.
eg::
if I have stored data into table
bike_table
======================================
bike_name bike_prefix bike_line
V111 V 111
W222 W 222
X333 X 333
===========================================
if some other time if query is made for same table data might look like this
bike_table
======================================
bike_name bike_prefix bike_line
W111 V 111
X222 W 222
X333 X 333
===========================================
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.
Thanks and Regards,
Sarita
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-03 17:18 Christophe Pettus <xof@thebuild.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
3 siblings, 0 replies; 25+ messages in thread
From: Christophe Pettus @ 2022-03-03 17:18 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: pgsql-sql@lists.postgresql.org
> On Mar 3, 2022, at 08:45, Sarita Sharma <saritakumarisharma61@gmail.com> wrote:
>
> 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.
> eg::
> if I have stored data into table
> bike_table
> ======================================
> bike_name bike_prefix bike_line
> V111 V 111
> W222 W 222
> X333 X 333
> ===========================================
>
> if some other time if query is made for same table data might look like this
> bike_table
> ======================================
> bike_name bike_prefix bike_line
> W111 V 111
> X222 W 222
> X333 X 333
> ===========================================
> 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?
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-03 17:24 MichaelDBA Vitale <michaeldba@sqlexec.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
3 siblings, 0 replies; 25+ messages in thread
From: MichaelDBA Vitale @ 2022-03-03 17:24 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; pgsql-sql@lists.postgresql.org
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div class="default-style">
Hi Sarita,
</div>
<div class="default-style">
<br>
</div>
<div>
Well, I doubt we will take this as a bug in PG at the getgo. I very seriously doubt this is a bug due to some PG internal toggling wrangling going on. I think we can get to the bottom of this if you provide more info in this thread.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Would you provide the DDL you used to create this table, along with any triggers under the covers?
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Then later, we might need to turn on some debugging in the PG log so we can capture any DML changes to this table to see if that is the culprit.
</div>
<div class="default-style">
log_statement = 'mod'
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Regards,
</div>
<div class="default-style">
Michael Vitale
</div>
<div class="default-style">
<br>
</div>
<blockquote type="cite">
<div>
On 03/03/2022 11:45 AM Sarita Sharma <saritakumarisharma61@gmail.com> wrote:
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div dir="ltr">
Hi Team,
<div>
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.
</div>
<div>
eg::
</div>
<div>
if I have stored data into table
</div>
<div>
bike_table
</div>
<div>
======================================
</div>
<div>
bike_name bike_prefix bike_line
</div>
<div>
V111 V 111
</div>
<div>
W222 W 222
<br>
</div>
<div>
X333 X 333
<br>
</div>
<div>
===========================================
</div>
<div>
<br>
</div>
<div>
if some other time if query is made for same table data might look like this
</div>
<div>
<div>
bike_table
</div>
<div>
======================================
</div>
<div>
bike_name bike_prefix bike_line
</div>
<div>
W111 V 111
</div>
<div>
X222 W 222
<br>
</div>
<div>
X333 X 333
<br>
</div>
<div>
===========================================
</div>
</div>
<div>
So usually bike_name keep changing its name thats seems to me a toggling behaviour.
</div>
<div>
Please take this issue as bug and work on this.
</div>
<div>
<br>
</div>
<div>
Thanks and Regards,
</div>
<div>
Sarita
</div>
</div>
</blockquote>
</body>
</html>
^ permalink raw reply [nested|flat] 25+ messages in thread
* RE: Bug in tables column data in postgres database
@ 2022-03-03 18:06 Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
3 siblings, 1 reply; 25+ messages in thread
From: Voillequin, Jean-Marc @ 2022-03-03 18:06 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; pgsql-sql@lists.postgresql.org <pgsql-sql@lists.postgresql.org>
Hello,
Are-you alone to work on this database?
Could you check with a:
select * from pg_stat_activity;
Regards
From: Sarita Sharma <saritakumarisharma61@gmail.com>
Sent: Thursday, March 3, 2022 5:46 PM
To: pgsql-sql@lists.postgresql.org
Subject: Bug in tables column data in postgres database
CAUTION: This email originated from outside of Moody's. Do not click links or open attachments unless you recognize the sender and know the content is safe.
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.
eg::
if I have stored data into table
bike_table
======================================
bike_name bike_prefix bike_line
V111 V 111
W222 W 222
X333 X 333
===========================================
if some other time if query is made for same table data might look like this
bike_table
======================================
bike_name bike_prefix bike_line
W111 V 111
X222 W 222
X333 X 333
===========================================
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.
Thanks and Regards,
Sarita
-----------------------------------------
Moody's monitors email communications through its networks for regulatory compliance purposes and to protect its customers, employees and business and where allowed to do so by applicable law. The information contained in this e-mail message, and any attachment thereto, is confidential and may not be disclosed without our express permission. If you are not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution or copying of this message, or any attachment thereto, in whole or in part, is strictly prohibited. If you have received this message in error, please immediately notify us by telephone, fax or e-mail and delete the message and all of its attachments. Every effort is made to keep our network free from viruses. You should, however, review this e-mail message, as well as any attachment thereto, for viruses. We take no responsibility and have no liability for any computer virus which may be transferred via this e-mail message.
-----------------------------------------
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-03 18:41 Sarita Sharma <saritakumarisharma61@gmail.com>
parent: Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>
0 siblings, 2 replies; 25+ messages in thread
From: Sarita Sharma @ 2022-03-03 18:41 UTC (permalink / raw)
To: Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; +Cc: pgsql-sql@lists.postgresql.org
Dear Sir,
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 .
Thankyou
On Thu, 3 Mar 2022, 23:36 Voillequin, Jean-Marc, <
Jean-Marc.Voillequin@moodys.com> wrote:
> Hello,
>
>
>
> Are-you alone to work on this database?
>
>
>
> Could you check with a:
>
> select * from pg_stat_activity;
>
>
>
> Regards
>
>
>
> *From:* Sarita Sharma <saritakumarisharma61@gmail.com>
> *Sent:* Thursday, March 3, 2022 5:46 PM
> *To:* pgsql-sql@lists.postgresql.org
> *Subject:* Bug in tables column data in postgres database
>
>
>
>
>
> *CAUTION:* This email originated from outside of Moody's. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
>
> 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.
>
> eg::
>
> if I have stored data into table
>
> bike_table
>
> ======================================
>
> bike_name bike_prefix bike_line
>
> V111 V 111
>
> W222 W 222
>
> X333 X 333
>
> ===========================================
>
>
>
> if some other time if query is made for same table data might look like
> this
>
> bike_table
>
> ======================================
>
> bike_name bike_prefix bike_line
>
> W111 V 111
>
> X222 W 222
>
> X333 X 333
>
> ===========================================
>
> 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.
>
>
>
> Thanks and Regards,
>
> Sarita
> -----------------------------------------
> Moody's monitors email communications through its networks for regulatory
> compliance purposes and to protect its customers, employees and business
> and where allowed to do so by applicable law. The information contained in
> this e-mail message, and any attachment thereto, is confidential and may
> not be disclosed without our express permission. If you are not the
> intended recipient or an employee or agent responsible for delivering this
> message to the intended recipient, you are hereby notified that you have
> received this message in error and that any review, dissemination,
> distribution or copying of this message, or any attachment thereto, in
> whole or in part, is strictly prohibited. If you have received this message
> in error, please immediately notify us by telephone, fax or e-mail and
> delete the message and all of its attachments. Every effort is made to keep
> our network free from viruses. You should, however, review this e-mail
> message, as well as any attachment thereto, for viruses. We take no
> responsibility and have no liability for any computer virus which may be
> transferred via this e-mail message.
> -----------------------------------------
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-03 19:24 Rob Sargent <robjsargent@gmail.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
1 sibling, 0 replies; 25+ messages in thread
From: Rob Sargent @ 2022-03-03 19:24 UTC (permalink / raw)
To: pgsql-sql@lists.postgresql.org
On 3/3/22 11:41, Sarita Sharma wrote:
> Dear Sir,
> 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 .
>
>
It's pretty safe to say the problem is in your Java code but you haven't
shown any constructive yet so no one can help you.
This isn't really a java discussion list but there are people here who
use the language and may be able to help. You might also try a JPA list.
You might try capturing the sql generated from your JPA code as that
(sql) is where this list truly shines.
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-03 19:27 David G. Johnston <david.g.johnston@gmail.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
1 sibling, 1 reply; 25+ messages in thread
From: David G. Johnston @ 2022-03-03 19:27 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
On Thu, Mar 3, 2022 at 12:13 PM Sarita Sharma <
saritakumarisharma61@gmail.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.
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-03 20:03 Steve Midgley <science@misuse.org>
parent: David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: Steve Midgley @ 2022-03-03 20:03 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Sarita Sharma <saritakumarisharma61@gmail.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
On Thu, Mar 3, 2022 at 11:27 AM David G. Johnston <
david.g.johnston@gmail.com> wrote:
> On Thu, Mar 3, 2022 at 12:13 PM Sarita Sharma <
> saritakumarisharma61@gmail.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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-04 14:04 Sarita Sharma <saritakumarisharma61@gmail.com>
parent: Steve Midgley <science@misuse.org>
0 siblings, 2 replies; 25+ messages in thread
From: Sarita Sharma @ 2022-03-04 14:04 UTC (permalink / raw)
To: Steve Midgley <science@misuse.org>; +Cc: David G. Johnston <david.g.johnston@gmail.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
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@misuse.org> wrote:
>
>
> On Thu, Mar 3, 2022 at 11:27 AM David G. Johnston <
> david.g.johnston@gmail.com> wrote:
>
>> On Thu, Mar 3, 2022 at 12:13 PM Sarita Sharma <
>> saritakumarisharma61@gmail.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
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-04 14:33 Erik Brandsberg <erik@heimdalldata.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
1 sibling, 1 reply; 25+ messages in thread
From: Erik Brandsberg @ 2022-03-04 14:33 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: Steve Midgley <science@misuse.org>; David G. Johnston <david.g.johnston@gmail.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
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@gmail.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@misuse.org> wrote:
>
>>
>>
>> On Thu, Mar 3, 2022 at 11:27 AM David G. Johnston <
>> david.g.johnston@gmail.com> wrote:
>>
>>> On Thu, Mar 3, 2022 at 12:13 PM Sarita Sharma <
>>> saritakumarisharma61@gmail.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
>>
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-04 14:43 Tom Lane <tgl@sss.pgh.pa.us>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
1 sibling, 0 replies; 25+ messages in thread
From: Tom Lane @ 2022-03-04 14:43 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: Steve Midgley <science@misuse.org>; David G. Johnston <david.g.johnston@gmail.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-04 14:52 Steve Midgley <science@misuse.org>
parent: Erik Brandsberg <erik@heimdalldata.com>
0 siblings, 1 reply; 25+ messages in thread
From: Steve Midgley @ 2022-03-04 14:52 UTC (permalink / raw)
To: Erik Brandsberg <erik@heimdalldata.com>; +Cc: Sarita Sharma <saritakumarisharma61@gmail.com>; David G. Johnston <david.g.johnston@gmail.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
On Fri, Mar 4, 2022, 6:33 AM Erik Brandsberg <erik@heimdalldata.com> wrote:
> 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@gmail.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@misuse.org> wrote:
>>
>>>
>>>
>>> On Thu, Mar 3, 2022 at 11:27 AM David G. Johnston <
>>> david.g.johnston@gmail.com> wrote:
>>>
>>>> On Thu, Mar 3, 2022 at 12:13 PM Sarita Sharma <
>>>> saritakumarisharma61@gmail.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
>>>
>>
I would add a little to this point. Whether it is postgres or it isn't, the
steps to debug are the same. The easiest first step is to instrument your
Java layer with something like New Relic and to start capturing your
postgres transaction log and feeding it to to an analysis environment of
some kind.
Then start filtering for activity that will show changes to the data in
question. We all are confident this is not postgres core. But I am even
more confident it is not postgres core doing this silently with no evidence
in the transaction log. So look for activity in New Relic and pg
transactions that will show you when this is happening. It should be easier
to identify the issue then.
I also on occasion work for well recognized companies - and I see
spectacular errors in those development processes. The difference is that
they have extensive quality processes to catch issues before they go to
production. Ideally you can also draw on those resources to help you here.
Simplify and instrument your environment. Use analytic tools. Develop steps
to reproduce (and steps where the problem won't manifest. Let that guide
your problem identification. Seek help internally from those with expertise
of your product, the code, and the systems.
Steve
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 08:04 Sarita Sharma <saritakumarisharma61@gmail.com>
parent: Steve Midgley <science@misuse.org>
0 siblings, 2 replies; 25+ messages in thread
From: Sarita Sharma @ 2022-03-05 08:04 UTC (permalink / raw)
To: Steve Midgley <science@misuse.org>; +Cc: Erik Brandsberg <erik@heimdalldata.com>; David G. Johnston <david.g.johnston@gmail.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
Hello Team,
I don't understand why Java layer is involved here. If data is saved in
database table and with a select query wherever result will come that only
getting fetched from java layers as a result set.
If toggling behaviour is observed by me in tables column of postgres
database then how Java layer involvement comes.
At last my point of view is:
Here I have reported something that seems to a bug as I observe some
toggling behaviour . Just as a user only I have reported. And its all upto
postres db team to take it into consideration or not instead of pointing
out java layers.
Upto this much responses I got I didn't got satisfied reply.
Thankyou
On Fri, 4 Mar 2022, 20:22 Steve Midgley, <science@misuse.org> wrote:
>
>
> On Fri, Mar 4, 2022, 6:33 AM Erik Brandsberg <erik@heimdalldata.com>
> wrote:
>
>> 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@gmail.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@misuse.org> wrote:
>>>
>>>>
>>>>
>>>> On Thu, Mar 3, 2022 at 11:27 AM David G. Johnston <
>>>> david.g.johnston@gmail.com> wrote:
>>>>
>>>>> On Thu, Mar 3, 2022 at 12:13 PM Sarita Sharma <
>>>>> saritakumarisharma61@gmail.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
>>>>
>>>
> I would add a little to this point. Whether it is postgres or it isn't,
> the steps to debug are the same. The easiest first step is to instrument
> your Java layer with something like New Relic and to start capturing your
> postgres transaction log and feeding it to to an analysis environment of
> some kind.
>
> Then start filtering for activity that will show changes to the data in
> question. We all are confident this is not postgres core. But I am even
> more confident it is not postgres core doing this silently with no evidence
> in the transaction log. So look for activity in New Relic and pg
> transactions that will show you when this is happening. It should be easier
> to identify the issue then.
>
> I also on occasion work for well recognized companies - and I see
> spectacular errors in those development processes. The difference is that
> they have extensive quality processes to catch issues before they go to
> production. Ideally you can also draw on those resources to help you here.
>
> Simplify and instrument your environment. Use analytic tools. Develop
> steps to reproduce (and steps where the problem won't manifest. Let that
> guide your problem identification. Seek help internally from those with
> expertise of your product, the code, and the systems.
>
> Steve
>
>>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 08:15 David G. Johnston <david.g.johnston@gmail.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
1 sibling, 1 reply; 25+ messages in thread
From: David G. Johnston @ 2022-03-05 08:15 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
On Sat, Mar 5, 2022 at 1:04 AM Sarita Sharma <saritakumarisharma61@gmail.com>
wrote:
> Here I have reported something that seems to a bug as I observe some
> toggling behaviour . Just as a user only I have reported. And its all upto
> postres db team to take it into consideration or not instead of pointing
> out java layers.
>
> Upto this much responses I got I didn't got satisfied reply.
>
>
The bottom line is that, yes, you've reported a bug. No one here has been
able to reproduce that bug on their machine. Without reproduction it is
not possible to solve. If that isn't satisfactory maybe you should reply
with exactly what you expect from us. Because as it stands your bug report
has been "closed" with a note of "unable to reproduce". As a developer of
software yourself you should be able to appreciate this as being a valid
result to a bug report.
David J.
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 08:29 Sarita Sharma <saritakumarisharma61@gmail.com>
parent: David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: Sarita Sharma @ 2022-03-05 08:29 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
Hello Team,
As I said it's a toggling behaviour it means when data will come like this
is not certain. All the times we can't expect it will come.
But what I observed , I already explained as a "select query " of table in
my first email, it's coming but it's not coming regularly. And when with
select query data will coming like that it's not certain so only I told it
a toggling behaviour.
But the thing is the most used column of the table usually shown such
behaviour.
I have only explained my observation on this platform in my first email
itself.
Thankyou
On Sat, 5 Mar 2022, 13:45 David G. Johnston, <david.g.johnston@gmail.com>
wrote:
> On Sat, Mar 5, 2022 at 1:04 AM Sarita Sharma <
> saritakumarisharma61@gmail.com> wrote:
>
>> Here I have reported something that seems to a bug as I observe some
>> toggling behaviour . Just as a user only I have reported. And its all upto
>> postres db team to take it into consideration or not instead of pointing
>> out java layers.
>>
>> Upto this much responses I got I didn't got satisfied reply.
>>
>>
> The bottom line is that, yes, you've reported a bug. No one here has been
> able to reproduce that bug on their machine. Without reproduction it is
> not possible to solve. If that isn't satisfactory maybe you should reply
> with exactly what you expect from us. Because as it stands your bug report
> has been "closed" with a note of "unable to reproduce". As a developer of
> software yourself you should be able to appreciate this as being a valid
> result to a bug report.
>
> David J.
>
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 08:40 Thomas Kellerer <shammat@gmx.net>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
3 siblings, 0 replies; 25+ messages in thread
From: Thomas Kellerer @ 2022-03-05 08:40 UTC (permalink / raw)
To: pgsql-sql@lists.postgresql.org
Sarita Sharma schrieb am 03.03.2022 um 17:45:
> 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.
> eg::
> if I have stored data into table
> bike_table
> ======================================
> bike_name bike_prefix bike_line
> V111 V 111
> W222 W 222
> X333 X 333
> ===========================================
>
> if some other time if query is made for same table data might look like this
> bike_table
> ======================================
> bike_name bike_prefix bike_line
> W111 V 111
> X222 W 222
> X333 X 333
> ===========================================
> 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.
It's extremely unlikely that this is a Postgres bug.
What is more likely is, that somewhere in your Java code the values get switched.
One way to find out, is to enable logging of all generated SQL statements
in your Java application. You mentioned JPA, so you are likely to use Hibernate.
This can e.g. be done using:
spring.jpa.show-sql=true
spring.jpa.properties.hibernate.format_sql=true
alternatively do it through the configuration of your logging framework.
You can also use "show_sql" in your persistence.xml if I'm not mistaken
(I don't know the details I keep away from obfuscation layers)
Another option is to turn on logging of all DML statements on the Postgres
side, using "log_statement=mod" in postgresql.conf
I am pretty sure with either one of those approaches you will see
that your application actively sends DML statements that change the data
in the database.
Thomas
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 08:51 David G. Johnston <david.g.johnston@gmail.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: David G. Johnston @ 2022-03-05 08:51 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
On Saturday, March 5, 2022, Sarita Sharma <saritakumarisharma61@gmail.com>
wrote:
> Hello Team,
> As I said it's a toggling behaviour it means when data will come like this
> is not certain. All the times we can't expect it will come.
> But what I observed , I already explained as a "select query " of table in
> my first email, it's coming but it's not coming regularly. And when with
> select query data will coming like that it's not certain so only I told it
> a toggling behaviour.
> But the thing is the most used column of the table usually shown such
> behaviour.
>
> I have only explained my observation on this platform in my first email
> itself.
>
And as I said your report has been noted and determined unable to replicate.
You are welcome to accept or ignore the offered free advice being provided
as to how to maybe get a better bug report produced yourself, hire your own
person to figure things out while having direct access to your systems, or
ignore the problem and live with its consequences. But repeating the exact
same emails will not magically result in a different outcome.
David J.
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 10:10 mgbii bax <gezeala@gmail.com>
parent: David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: mgbii bax @ 2022-03-05 10:10 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Sarita Sharma <saritakumarisharma61@gmail.com>; Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
Probably caused by wrong connection settings or in a transition, no commit
was issued. Or, a crash may be happening with quick, unnoticeable start up.
On Sat, Mar 5, 2022, 12:51 AM David G. Johnston <david.g.johnston@gmail.com>
wrote:
> On Saturday, March 5, 2022, Sarita Sharma <saritakumarisharma61@gmail.com>
> wrote:
>
>> Hello Team,
>> As I said it's a toggling behaviour it means when data will come like
>> this is not certain. All the times we can't expect it will come.
>> But what I observed , I already explained as a "select query " of table
>> in my first email, it's coming but it's not coming regularly. And when with
>> select query data will coming like that it's not certain so only I told it
>> a toggling behaviour.
>> But the thing is the most used column of the table usually shown such
>> behaviour.
>>
>> I have only explained my observation on this platform in my first email
>> itself.
>>
>
> And as I said your report has been noted and determined unable to
> replicate.
>
> You are welcome to accept or ignore the offered free advice being provided
> as to how to maybe get a better bug report produced yourself, hire your own
> person to figure things out while having direct access to your systems, or
> ignore the problem and live with its consequences. But repeating the exact
> same emails will not magically result in a different outcome.
>
> David J.
>
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 10:28 Sarita Sharma <saritakumarisharma61@gmail.com>
parent: mgbii bax <gezeala@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: Sarita Sharma @ 2022-03-05 10:28 UTC (permalink / raw)
To: mgbii bax <gezeala@gmail.com>; +Cc: David G. Johnston <david.g.johnston@gmail.com>; Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
Thankyou all for your explanation.
I am only hoping that some point of time the bug reported by me will get
reproduced from your end and you will find time to work on this.
On Sat, 5 Mar 2022, 15:40 mgbii bax, <gezeala@gmail.com> wrote:
> Probably caused by wrong connection settings or in a transition, no commit
> was issued. Or, a crash may be happening with quick, unnoticeable start up.
>
> On Sat, Mar 5, 2022, 12:51 AM David G. Johnston <
> david.g.johnston@gmail.com> wrote:
>
>> On Saturday, March 5, 2022, Sarita Sharma <saritakumarisharma61@gmail.com>
>> wrote:
>>
>>> Hello Team,
>>> As I said it's a toggling behaviour it means when data will come like
>>> this is not certain. All the times we can't expect it will come.
>>> But what I observed , I already explained as a "select query " of table
>>> in my first email, it's coming but it's not coming regularly. And when with
>>> select query data will coming like that it's not certain so only I told it
>>> a toggling behaviour.
>>> But the thing is the most used column of the table usually shown such
>>> behaviour.
>>>
>>> I have only explained my observation on this platform in my first email
>>> itself.
>>>
>>
>> And as I said your report has been noted and determined unable to
>> replicate.
>>
>> You are welcome to accept or ignore the offered free advice being
>> provided as to how to maybe get a better bug report produced yourself, hire
>> your own person to figure things out while having direct access to your
>> systems, or ignore the problem and live with its consequences. But
>> repeating the exact same emails will not magically result in a different
>> outcome.
>>
>> David J.
>>
>>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 15:27 David G. Johnston <david.g.johnston@gmail.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: David G. Johnston @ 2022-03-05 15:27 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: mgbii bax <gezeala@gmail.com>; Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
On Sat, Mar 5, 2022 at 3:29 AM Sarita Sharma <saritakumarisharma61@gmail.com>
wrote:
>
> I am only hoping that some point of time the bug reported by me will get
> reproduced from your end and you will find time to work on this.
>
>>
>>>
I can assure you that absent further feedback and details from you no one
will be working on this. Hundreds of thousands of people have hundreds, if
not thousands, of tables, in production databases, running 24x7x365, and do
not experience this behavior. The problem is specific to your organization
and thus your organization's responsibility.
David J.
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 15:56 Sarita Sharma <saritakumarisharma61@gmail.com>
parent: David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 2 replies; 25+ messages in thread
From: Sarita Sharma @ 2022-03-05 15:56 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: mgbii bax <gezeala@gmail.com>; Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
As of now I think I only faced this issue in postgres database behavioural
issue. In future ofcourse more developers might face such issue.
All the best team.
On Sat, 5 Mar 2022, 20:57 David G. Johnston, <david.g.johnston@gmail.com>
wrote:
> On Sat, Mar 5, 2022 at 3:29 AM Sarita Sharma <
> saritakumarisharma61@gmail.com> wrote:
>
>>
>> I am only hoping that some point of time the bug reported by me will get
>> reproduced from your end and you will find time to work on this.
>>
>>>
>>>>
> I can assure you that absent further feedback and details from you no one
> will be working on this. Hundreds of thousands of people have hundreds, if
> not thousands, of tables, in production databases, running 24x7x365, and do
> not experience this behavior. The problem is specific to your organization
> and thus your organization's responsibility.
>
> David J.
>
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-05 16:07 David G. Johnston <david.g.johnston@gmail.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
1 sibling, 0 replies; 25+ messages in thread
From: David G. Johnston @ 2022-03-05 16:07 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: mgbii bax <gezeala@gmail.com>; Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
On Saturday, March 5, 2022, Sarita Sharma <saritakumarisharma61@gmail.com>
wrote:
> As of now I think I only faced this issue in postgres database behavioural
> issue. In future ofcourse more developers might face such issue.
>
What exact versions of PostgreSQL and Operating System are you running?
Has this database ever gone through pg_upgrade (i.e., what is its history)?
Why did you send this to our -sql list instead of -bugs (or use our bug
reporting form)? I mean, it is a poorly produced bug report (there is a
link to a page from our bug reporting form that describes what makes for a
actionable bug report) but you do continue to insist that it is a bug.
David J.
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-06 10:08 Sándor Daku <daku.sandor@gmail.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
1 sibling, 0 replies; 25+ messages in thread
From: Sándor Daku @ 2022-03-06 10:08 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: pgsql-sql <pgsql-sql@lists.postgresql.org>
On Sun, 6 Mar 2022 at 00:14, Sarita Sharma <saritakumarisharma61@gmail.com>
wrote:
> As of now I think I only faced this issue in postgres database behavioural
> issue. In future ofcourse more developers might face such issue.
>
>
> All the best team.
>
> On Sat, 5 Mar 2022, 20:57 David G. Johnston, <david.g.johnston@gmail.com>
> wrote:
>
>> On Sat, Mar 5, 2022 at 3:29 AM Sarita Sharma <
>> saritakumarisharma61@gmail.com> wrote:
>>
>>>
>>> I am only hoping that some point of time the bug reported by me will get
>>> reproduced from your end and you will find time to work on this.
>>>
>>>>
>>>>>
>> I can assure you that absent further feedback and details from you no one
>> will be working on this. Hundreds of thousands of people have hundreds, if
>> not thousands, of tables, in production databases, running 24x7x365, and do
>> not experience this behavior. The problem is specific to your organization
>> and thus your organization's responsibility.
>>
>> David J.
>>
>>
Hi,
What you are telling to us is not a simple bug. It's something that would
make Postgres completely unusable as a database. Luckily nobody experienced
it so far except you.(Mind you, people on this list have countless hours of
experience building, running and maintaining Postgres databases and I don't
even dare to guess how much data that means.)
It is analogous with telling the Java core developers that if statement
doesn't work correctly, it messes up the evaluation of the condition
sometimes.
It's highly unlikely. And this is the only thing we can tell you without
further information about your issue.
So if you want our help, please provide us at least the table definition
and the select statement producing the wrong result.
On top of that log and check the dml statements on your database to see if
something modifies the data without your knowledge.
Regards,
Sándor
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-06 12:23 Michaeldba@sqlexec.com <Michaeldba@sqlexec.com>
parent: Sarita Sharma <saritakumarisharma61@gmail.com>
1 sibling, 1 reply; 25+ messages in thread
From: Michaeldba@sqlexec.com @ 2022-03-06 12:23 UTC (permalink / raw)
To: Sarita Sharma <saritakumarisharma61@gmail.com>; +Cc: Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; David G. Johnston <david.g.johnston@gmail.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
You are not doing what we have asked you to do.
I asked you to send me the ddl for the table including any triggers and also asked you to turn on debugging to capture dml changes (log_statement=mod) and you didn’t do it.
You are not cooperating with all the folks that tried to help you.
Sent from my iPad
> On Mar 5, 2022, at 6:14 PM, Sarita Sharma <saritakumarisharma61@gmail.com> wrote:
>
>
> Hello Team,
> I don't understand why Java layer is involved here. If data is saved in database table and with a select query wherever result will come that only getting fetched from java layers as a result set.
>
> If toggling behaviour is observed by me in tables column of postgres database then how Java layer involvement comes.
>
> At last my point of view is:
> Here I have reported something that seems to a bug as I observe some toggling behaviour . Just as a user only I have reported. And its all upto postres db team to take it into consideration or not instead of pointing out java layers.
>
> Upto this much responses I got I didn't got satisfied reply.
>
>
> Thankyou
>
>
>
>> On Fri, 4 Mar 2022, 20:22 Steve Midgley, <science@misuse.org> wrote:
>>
>>
>>> On Fri, Mar 4, 2022, 6:33 AM Erik Brandsberg <erik@heimdalldata.com> wrote:
>>> 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@gmail.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@misuse.org> wrote:
>>>>>
>>>>>
>>>>>> On Thu, Mar 3, 2022 at 11:27 AM David G. Johnston <david.g.johnston@gmail.com> wrote:
>>>>>>> On Thu, Mar 3, 2022 at 12:13 PM Sarita Sharma <saritakumarisharma61@gmail.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
>>
>>
>> I would add a little to this point. Whether it is postgres or it isn't, the steps to debug are the same. The easiest first step is to instrument your Java layer with something like New Relic and to start capturing your postgres transaction log and feeding it to to an analysis environment of some kind.
>>
>> Then start filtering for activity that will show changes to the data in question. We all are confident this is not postgres core. But I am even more confident it is not postgres core doing this silently with no evidence in the transaction log. So look for activity in New Relic and pg transactions that will show you when this is happening. It should be easier to identify the issue then.
>>
>> I also on occasion work for well recognized companies - and I see spectacular errors in those development processes. The difference is that they have extensive quality processes to catch issues before they go to production. Ideally you can also draw on those resources to help you here.
>>
>> Simplify and instrument your environment. Use analytic tools. Develop steps to reproduce (and steps where the problem won't manifest. Let that guide your problem identification. Seek help internally from those with expertise of your product, the code, and the systems.
>>
>> Steve
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Bug in tables column data in postgres database
@ 2022-03-06 13:49 Sarita Sharma <saritakumarisharma61@gmail.com>
parent: Michaeldba@sqlexec.com <Michaeldba@sqlexec.com>
0 siblings, 0 replies; 25+ messages in thread
From: Sarita Sharma @ 2022-03-06 13:49 UTC (permalink / raw)
To: Michaeldba@sqlexec.com; +Cc: Steve Midgley <science@misuse.org>; Erik Brandsberg <erik@heimdalldata.com>; David G. Johnston <david.g.johnston@gmail.com>; Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
Sorry, today l m not feeling good. Tomorrow I will reply you with all the
points you have asked me to do.
Thanks and Regards,
Sarita
On Sun, 6 Mar 2022, 17:53 Michaeldba@sqlexec.com, <Michaeldba@sqlexec.com>
wrote:
> You are not doing what we have asked you to do.
>
> I asked you to send me the ddl for the table including any triggers and
> also asked you to turn on debugging to capture dml changes
> (log_statement=mod) and you didn’t do it.
>
> You are not cooperating with all the folks that tried to help you.
>
> Sent from my iPad
>
> On Mar 5, 2022, at 6:14 PM, Sarita Sharma <saritakumarisharma61@gmail.com>
> wrote:
>
>
> Hello Team,
> I don't understand why Java layer is involved here. If data is saved in
> database table and with a select query wherever result will come that only
> getting fetched from java layers as a result set.
>
> If toggling behaviour is observed by me in tables column of postgres
> database then how Java layer involvement comes.
>
> At last my point of view is:
> Here I have reported something that seems to a bug as I observe some
> toggling behaviour . Just as a user only I have reported. And its all upto
> postres db team to take it into consideration or not instead of pointing
> out java layers.
>
> Upto this much responses I got I didn't got satisfied reply.
>
>
> Thankyou
>
>
>
> On Fri, 4 Mar 2022, 20:22 Steve Midgley, <science@misuse.org> wrote:
>
>>
>>
>> On Fri, Mar 4, 2022, 6:33 AM Erik Brandsberg <erik@heimdalldata.com>
>> wrote:
>>
>>> 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@gmail.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@misuse.org> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 3, 2022 at 11:27 AM David G. Johnston <
>>>>> david.g.johnston@gmail.com> wrote:
>>>>>
>>>>>> On Thu, Mar 3, 2022 at 12:13 PM Sarita Sharma <
>>>>>> saritakumarisharma61@gmail.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
>>>>>
>>>>
>> I would add a little to this point. Whether it is postgres or it isn't,
>> the steps to debug are the same. The easiest first step is to instrument
>> your Java layer with something like New Relic and to start capturing your
>> postgres transaction log and feeding it to to an analysis environment of
>> some kind.
>>
>> Then start filtering for activity that will show changes to the data in
>> question. We all are confident this is not postgres core. But I am even
>> more confident it is not postgres core doing this silently with no evidence
>> in the transaction log. So look for activity in New Relic and pg
>> transactions that will show you when this is happening. It should be easier
>> to identify the issue then.
>>
>> I also on occasion work for well recognized companies - and I see
>> spectacular errors in those development processes. The difference is that
>> they have extensive quality processes to catch issues before they go to
>> production. Ideally you can also draw on those resources to help you here.
>>
>> Simplify and instrument your environment. Use analytic tools. Develop
>> steps to reproduce (and steps where the problem won't manifest. Let that
>> guide your problem identification. Seek help internally from those with
>> expertise of your product, the code, and the systems.
>>
>> Steve
>>
>>>
^ permalink raw reply [nested|flat] 25+ messages in thread
end of thread, other threads:[~2022-03-06 13:49 UTC | newest]
Thread overview: 25+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-03-03 16:45 Bug in tables column data in postgres database Sarita Sharma <saritakumarisharma61@gmail.com>
2022-03-03 17:18 ` Christophe Pettus <xof@thebuild.com>
2022-03-03 17:24 ` MichaelDBA Vitale <michaeldba@sqlexec.com>
2022-03-03 18:06 ` Voillequin, Jean-Marc <Jean-Marc.Voillequin@moodys.com>
2022-03-03 18:41 ` Sarita Sharma <saritakumarisharma61@gmail.com>
2022-03-03 19:24 ` Rob Sargent <robjsargent@gmail.com>
2022-03-03 19:27 ` David G. Johnston <david.g.johnston@gmail.com>
2022-03-03 20:03 ` Steve Midgley <science@misuse.org>
2022-03-04 14:04 ` Sarita Sharma <saritakumarisharma61@gmail.com>
2022-03-04 14:33 ` Erik Brandsberg <erik@heimdalldata.com>
2022-03-04 14:52 ` Steve Midgley <science@misuse.org>
2022-03-05 08:04 ` Sarita Sharma <saritakumarisharma61@gmail.com>
2022-03-05 08:15 ` David G. Johnston <david.g.johnston@gmail.com>
2022-03-05 08:29 ` Sarita Sharma <saritakumarisharma61@gmail.com>
2022-03-05 08:51 ` David G. Johnston <david.g.johnston@gmail.com>
2022-03-05 10:10 ` mgbii bax <gezeala@gmail.com>
2022-03-05 10:28 ` Sarita Sharma <saritakumarisharma61@gmail.com>
2022-03-05 15:27 ` David G. Johnston <david.g.johnston@gmail.com>
2022-03-05 15:56 ` Sarita Sharma <saritakumarisharma61@gmail.com>
2022-03-05 16:07 ` David G. Johnston <david.g.johnston@gmail.com>
2022-03-06 10:08 ` Sándor Daku <daku.sandor@gmail.com>
2022-03-06 12:23 ` Michaeldba@sqlexec.com <Michaeldba@sqlexec.com>
2022-03-06 13:49 ` Sarita Sharma <saritakumarisharma61@gmail.com>
2022-03-04 14:43 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-03-05 08:40 ` Thomas Kellerer <shammat@gmx.net>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox