Regarding issue #6510

From: Pravesh Sharma <pravesh(dot)sharma(at)enterprisedb(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Regarding issue #6510
Date: 2025-05-20 05:16:07
Message-ID: CA+36bxGb7qik5gphraXht9gVpRuWV1ttEB8F5sptW3WTq6SOrw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Hackers,

I am working on issue #6510
<https://github.com/pgadmin-org/pgadmin4/issues/6510>, where the result
grid slows down and sometimes hangs when large JSON or text data is present
in a table column. Upon investigation, I found that this is due to
rendering the entire JSON to the DOM. This causes slowness, especially with
large datasets; for example, rendering a 15MB JSON object for preview
purposes is unnecessary. I am proposing a solution where the result grid
will render data up to a certain length. I have implemented these changes,
and everything is working fine, resulting in a significant performance
improvement. As you can see in the screenshot, the JSON data is 20MB, and
on the result grid, we are displaying only 200 characters as it is only a
preview. I am also considering making this maximum display length a user
preference, named "Max column data display length," allowing them to
customize how much data they want to see. Can you tell me what you think of
this approach or if you have any suggestions?

Thanks,

Pravesh

[image: image.png]
--

Pravesh Sharma

Senior SDE

+91 9406461406

enterprisedb.com

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Daulat 2025-05-20 13:02:41 pgAdmin4 Still Shows Old Version After Upgrade
Previous Message Aditya Toshniwal 2025-05-19 07:25:07 Re: Open Source Contribution