From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Sarita Sharma <saritakumarisharma61(at)gmail(dot)com> |
Cc: | 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 08:51:08 |
Message-ID: | CAKFQuwbdZkjaTmvNFk-7hLiO7iQUQdrOPNKhqgmu5XwTWMzN6w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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 | mgbii bax | 2022-03-05 10:10:25 | Re: Bug in tables column data in postgres database |
Previous Message | Thomas Kellerer | 2022-03-05 08:40:28 | Re: Bug in tables column data in postgres database |