| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Sarita Sharma <saritakumarisharma61(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:27:27 |
| Message-ID: | CAKFQuwa=xkKbDiMmiJtBdQo_-4AypLDC8O74sTdjhBgseETr=Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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 | Sarita Sharma | 2022-03-05 15:56:45 | Re: Bug in tables column data in postgres database |
| Previous Message | Sarita Sharma | 2022-03-05 10:28:56 | Re: Bug in tables column data in postgres database |