Re: suspected behavior with upgrade scenario : pagadmin 8.8

2024-06-05 Thread Usman Khan
+1 On Thu, Jun 6, 2024 at 10:41 AM Aditya Toshniwal < aditya.toshni...@enterprisedb.com> wrote: > Hi, > > We could think of avoiding duplicates if a server is already added on the > basis of server properties. > > On Thu, Jun 6, 2024 at 11:00 AM Anil Sahoo > wrote: > >> Hi Usman, >> Once you ins

Re: suspected behavior with upgrade scenario : pagadmin 8.8

2024-06-05 Thread Usman Khan
Hi Anil, Thanks for replying. Yes, I understand that it's auto-detected. That is why I did not report it for a bug. But circulating it through email, I wanted to open a discussion. Can we somehow avoid it? Otherwise, if there are more than one servers, it would be annoying for the user to have dupl

Re: suspected behavior with upgrade scenario : pagadmin 8.8

2024-06-05 Thread Aditya Toshniwal
Hi, We could think of avoiding duplicates if a server is already added on the basis of server properties. On Thu, Jun 6, 2024 at 11:00 AM Anil Sahoo wrote: > Hi Usman, > Once you install PostgreSQL 16 in your system and on opening pgAdmin 4, it > auto-detects the postgres servers installed in y

Re: suspected behavior with upgrade scenario : pagadmin 8.8

2024-06-05 Thread Anil Sahoo
Hi Usman, Once you install PostgreSQL 16 in your system and on opening pgAdmin 4, it auto-detects the postgres servers installed in your system. So that duplicate server you are saying is auto detected and the other one you added manually. To confirm this you can check by going through the steps,