Re: TOAST table performance problem

Yes, I would concur that this planning time and execution time do not
take into account the network time sending the data back to the client,
especially since your are sending back the entire contents of the table.

Regards,
Michael Vitale

Andreas Joseph Krogh wrote on 2/7/2020 8:41 AM:
> På fredag 07. februar 2020 kl. 14:23:35, skrev Asya Nevra Buyuksoy
> <ayisan1096(at)gmail(dot)com <mailto:ayisan1096(at)gmail(dot)com>>:
>
> Sorry for the misunderstanding.
> I have a table like;
> CREATE TABLE zamazin
> (
>   paramuser_id text,
>   paramperson_id integer,
>   paramdata json,
>   paramisdeleted boolean,
>   paramactiontime timestamp without time zone
> )
> paramdata row size is 110KB and over.
> When I execute this query like;
> *select * from zamazin*
> it takes *600 seconds*.
> But when analyze the query ;
> *"Seq Scan on public.zamazin  (cost=0.00..21.77 rows=1077
> width=49) (actual time=0.008..0.151 rows=1077 loops=1)"
> "  Output: paramuser_id, paramperson_id, paramdata,
> paramisdeleted, paramactiontime"
> "  Buffers: shared hit=11"
> "Planning time: 0.032 ms"
> "Execution time: 0.236 ms"*
>  Why the query takes a long time, I do not understand. I
> assume that this relates to the TOAST structure.
>
> My guess is the time is spent in the /client/ retrieving the data, not
> in the DB itself. Are you on a slow network?
> --
> *Andreas Joseph Krogh*
> CTO / Partner - Visena AS
> Mobile: +47 909 56 963
> andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
> www.visena.com <https://www.visena.com>
> <https://www.visena.com>