From: | Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com> |
---|---|
To: | Harald Fuchs <hari(dot)fuchs(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: execute same query only one time? |
Date: | 2016-02-09 12:07:04 |
Message-ID: | CAKOSWNmF4EWJY1V909iXfp7_Q-LRPYi2AAMkJGxPuQC+pKbGhg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/9/16, Harald Fuchs <hari(dot)fuchs(at)gmail(dot)com> wrote:
> Johannes <jotpe(at)posteo(dot)de> writes:
>
>>> What the reason to execute all statements which return different
>>> columns at once?
>>>
>>>> Saving roundtrips,
>>>
>>> In most cases they are not so big. Getting a bunch of duplicated data
>>> is wasting you network bandwidth and don't increase speed.
>>
>> In my and your example no duplicated data (result sets) is send over the
>> network. The server do not need to wait until the client snips out the
>> id and sends it id in the next query again. So the server can compute
>> the result set without external dependencies as fast as possible.
>
> Sounds like what you're really after is a stored procedure, isn't it?
Unfortunately, his case is different, because he needs to get two
different set of rows that is impossible even with stored procedures.
--
Best regards,
Vitaly Burovoy
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-02-09 12:51:50 | Re: fast refresh materialized view |
Previous Message | Geoff Winkless | 2016-02-09 11:42:44 | Re: COALESCE requires NULL from scalar subquery has a type |