| From: | Sarita Sharma <saritakumarisharma61(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | mgbii bax <gezeala(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 15:56:45 |
| Message-ID: | CAOKMkZrcngHUi2qUa3knqcVhFVuO=em2wVchV5d-JezTGqqveA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Sat, Mar 5, 2022 at 3:29 AM Sarita Sharma <
> saritakumarisharma61(at)gmail(dot)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.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-03-05 16:07:51 | Re: Bug in tables column data in postgres database |
| Previous Message | David G. Johnston | 2022-03-05 15:27:27 | Re: Bug in tables column data in postgres database |