From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | Asya Nevra Buyuksoy <ayisan1096(at)gmail(dot)com> |
Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: TOAST table performance problem |
Date: | 2020-02-07 15:15:48 |
Message-ID: | 9CE9EAEF-4DD1-4FCF-9B22-7609CBA83021@visena.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Try \o <filename> in psql, to redirect the output to file, and prevent it from processing the json (ie. format it)
Den 7. februar 2020 15:59:05 CET, skrev Asya Nevra Buyuksoy <ayisan1096(at)gmail(dot)com>:
>I try it, but there is no enhancement.
>I read this link is about TOAST and also its sub_links;
>https://blog.gojekengineering.com/a-toast-from-postgresql-83b83d0d0683
>When I execute this query, except JSON data like;
>SELECT paramuser_id, paramperson_id, paramisdeleted, paramactiontime
> FROM zamazin;
>It takes 94 ms. :)
>
>
>Andreas Joseph Krogh <andreas(at)visena(dot)com>, 7 Şub 2020 Cum, 17:42 tarihinde
>şunu yazdı:
>
>> På fredag 07. februar 2020 kl. 15:35:04, skrev Asya Nevra Buyuksoy <
>> ayisan1096(at)gmail(dot)com>:
>>
>> I use pgadmin3.
>>
>>
>> Try "psql", it has the lowest overhead (I think). pgAdmin might use time
>> presenting the results etc. which is easy to overlook.
>>
>> --
>> Andreas Joseph Krogh
>>
>>
--
Sendt fra min Android-enhet med K-9 e-post. Unnskyld min kortfattethet.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2020-02-07 16:09:47 | Re: proposal: schema variables |
Previous Message | Asya Nevra Buyuksoy | 2020-02-07 14:59:05 | Re: TOAST table performance problem |