Re: Dashboard background process not shown

2025-07-16 Thread Khushboo Vashi
Hi, Please provide screenshots for the tab that doesn't display and the tab in which you can see the process. On Wed, Jul 16, 2025 at 6:42 PM Wolfgang Baeck < wolfgang.ba...@symphonyai.com> wrote: > Hi Support, > > I noticed that for some time now my pgAdmin (9.5) doesn’t show background > proce

Dashboard background process not shown

2025-07-16 Thread Wolfgang Baeck
Hi Support, I noticed that for some time now my pgAdmin (9.5) doesn’t show background processes in the Dashboard tab and also not in the Processes tab anymore. I now need to go to the "State" tab when on the major "Dashboard" tab. When in the "Dashboard/Activity" tab, no processes are shown. I

Installation error

2025-07-16 Thread Praveen Rajakumar
Hi Team, I am trying to install PGADMIN4 on my Mac system, OS Sequoia 15.5. I am seeing the following error message. Please help me to fix the error. [image: Screenshot 2025-07-14 at 12.51.39 AM.png] Thanks, Praveen Rajakumar.

Re: Naming Object commands "Delete" is a source of user errors

2025-07-16 Thread Darren Duncan
On 2025-07-16 12:38 a.m., Ray O'Donnell wrote: On 16 July 2025 08:19:09 Darren Duncan wrote: I am finding that it is a recurring and damaging source of user error that Object/Explorer commands named "Delete" actually correspond to SQL DROP rather than SQL DELETE or TRUNCATE. Multiple times I ha

Re: Naming Object commands "Delete" is a source of user errors

2025-07-16 Thread Ray O'Donnell
On 16 July 2025 08:19:09 Darren Duncan wrote: I am finding that it is a recurring and damaging source of user error that Object/Explorer commands named "Delete" actually correspond to SQL DROP rather than SQL DELETE or TRUNCATE. Multiple times I have accidentally dropped tables when I meant t

Naming Object commands "Delete" is a source of user errors

2025-07-16 Thread Darren Duncan
I am finding that it is a recurring and damaging source of user error that Object/Explorer commands named "Delete" actually correspond to SQL DROP rather than SQL DELETE or TRUNCATE. Multiple times I have accidentally dropped tables when I meant to just truncate them. I created a GitHub issue