| 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 16:07:51 |
| Message-ID: | CAKFQuwZxPGkz4zsv5rJ9J+ajKTVyYe1NO9HmPN+_29sxSuYQHQ@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:
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sándor Daku | 2022-03-06 10:08:54 | Re: Bug in tables column data in postgres database |
| Previous Message | Sarita Sharma | 2022-03-05 15:56:45 | Re: Bug in tables column data in postgres database |