From: Luís Roberto Weck <luisroberto@siscobra.com.br>
To: ayisan1096@gmail.com
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Fwd: TOAST table performance problem
Date: Mon, 10 Feb 2020 09:31:30 -0300
Message-ID: <f3baba0f-e6c1-af73-e25e-49abcabb3ab7@siscobra.com.br> (raw)
In-Reply-To: <CADA48rGYxyrsrFE4jDPbKCYOinx93AmkP7pFyow+=b=k=Q--HA@mail.gmail.com>
References: <CADA48rEizH8wGCCRdfWQYT0q__jeDHFHHKMeb6Z=imqmfyQejw@mail.gmail.com>
<VisenaEmail.28.a032595c9fdf4345.17020191d94@tc7-visena>
<CADA48rGx3LRm84hT72_QK5MFvaQ26=4o7U75i7fDDpxYbYzVaA@mail.gmail.com>
<9CE9EAEF-4DD1-4FCF-9B22-7609CBA83021@visena.com>
<CADA48rFu27GmovbvqXe3jMZhY_ogh4jpTfH09mHrJTGXZX0w=g@mail.gmail.com>
<CADA48rGYxyrsrFE4jDPbKCYOinx93AmkP7pFyow+=b=k=Q--HA@mail.gmail.com>
> ---------- Forwarded message ---------
> Gönderen: *Asya Nevra Buyuksoy* <ayisan1096@gmail.com
> <mailto:ayisan1096@gmail.com>>
> Date: 10 Şub 2020 Pzt, 10:51
> Subject: Re: TOAST table performance problem
> To: Andreas Joseph Krogh <andreas@visena.com <mailto:andreas@visena.com>>
>
>
> I copied my data to the CSV file, yes it is very fast. However, this
> does not solve my problem.
> After deserializing the on the front side, I want to visualize my data
> on the web page effectively.
> When I select my data one by one with a limit clause, the query
> executes 200 ms. For example, If I create a function that takes data
> with a loop, the execution time will be 200 ms*1000=200 sec.
>
> Andreas Joseph Krogh <andreas@visena.com <mailto:andreas@visena.com>>,
> 7 Şub 2020 Cum, 18:15 tarihinde şunu yazdı:
>
> 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@gmail.com <mailto:ayisan1096@gmail.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@visena.com
> <mailto:andreas@visena.com>>, 7 Şub 2020 Cum, 17:42 tarihinde
> şunu yazdı:
>
> På fredag 07. februar 2020 kl. 15:35:04, skrev Asya Nevra
> Buyuksoy <ayisan1096@gmail.com <mailto:ayisan1096@gmail.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.
>
What Andreas is trying to say is that it's not PostgreSQL that is slow
to read the JSON, but your client app that is slow to parse it.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: luisroberto@siscobra.com.br, ayisan1096@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Fwd: TOAST table performance problem
In-Reply-To: <f3baba0f-e6c1-af73-e25e-49abcabb3ab7@siscobra.com.br>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox