From: | Sarita Sharma <saritakumarisharma61(at)gmail(dot)com> |
---|---|
To: | mgbii bax <gezeala(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Steve Midgley <science(at)misuse(dot)org>, Erik Brandsberg <erik(at)heimdalldata(dot)com>, "Voillequin, Jean-Marc" <Jean-Marc(dot)Voillequin(at)moodys(dot)com>, pgsql-sql <pgsql-sql(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Bug in tables column data in postgres database |
Date: | 2022-03-05 10:28:56 |
Message-ID: | CAOKMkZqyj=qBG3vy7PAMGMtM0e51LDfE01BEAohF-p4xm4H=oA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)gmail(dot)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(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> On Saturday, March 5, 2022, Sarita Sharma <saritakumarisharma61(at)gmail(dot)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.
>>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-03-05 15:27:27 | Re: Bug in tables column data in postgres database |
Previous Message | mgbii bax | 2022-03-05 10:10:25 | Re: Bug in tables column data in postgres database |