Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.databases.postgresql > #604

Re: Returning a table in SQL

Path csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news.netfront.net!gonzo.reversiblemaps.ath.cx!not-for-mail
From Jasen Betts <jasen@xnet.co.nz>
Newsgroups comp.databases.postgresql
Subject Re: Returning a table in SQL
Date 4 Sep 2014 11:21:37 GMT
Organization JJ's own news server
Lines 24
Message-ID <lu9i01$ka$1@gonzo.reversiblemaps.ath.cx> (permalink)
References <ltignr$1hgl$1@adenine.netfront.net> <c644cpF2g32U1@mid.individual.net> <ltlfj0$1702$1@adenine.netfront.net> <c691fnFahj8U1@mid.individual.net> <lu15ml$qq8$1@adenine.netfront.net> <lu1jc2$1j5$1@gonzo.reversiblemaps.ath.cx> <lu92hs$3ft$1@adenine.netfront.net>
NNTP-Posting-Host 118.90.91.91
X-Trace adenine.netfront.net 1409830240 18765 118.90.91.91 (4 Sep 2014 11:30:40 GMT)
X-Complaints-To news@netfront.net
NNTP-Posting-Date Thu, 4 Sep 2014 11:30:40 +0000 (UTC)
X-Face ?)Aw4rXwN5u0~$nqKj`xPz>xHCwgi^q+^?Ri*+R(&uv2=E1Q0Zk(>h!~o2ID@6{uf8s;a +M[5[U[QT7xFN%^gR"=tuJw%TXXR'Fp~W;(T"1(739R%m0Yyyv*gkGoPA.$b,D.w:z+<'"=-lVT?6 {T?=R^:W5g|E2#EhjKCa+nt":4b}dU7GYB*HBxn&Td$@f%.kl^:7X8rQWd[NTc"P"u6nkisze/Q;8 "9Z{peQF,w)7UjV$c|RO/mQW/NMgWfr5*$-Z%u46"/00mx-,\R'fLPe.)^
User-Agent slrn/pre1.0.0-18 (Linux)
Xref csiph.com comp.databases.postgresql:604

Show key headers only | View raw


On 2014-09-04, AP <unixpronospam@verizon.net> wrote:
> That a good, if obvious, point. Obvious because all indexing and 
> optimization would need to happen within whatever query is wrapped into this 
> parametrized view. That said, is there a way to build a useful index on a 
> record column ? On a record-returning function column ?
>
> And do all queries get same shot at optimization whether they come from 
> within a Plpgsql block or a cursor, or from within a SQL function or view ?

if you write the function to contain the where clause it can sometimes be as
efficient,

plpgsql functions don't get query time optimsation which saves time
but may cost efficiency. this may or may not help. evaluate can be
used to force optimisation.


views are bascially as efficient as writing it out in full.

-- 
umop apisdn


--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Back to comp.databases.postgresql | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Returning a table in SQL "AP" <unixpro-nospam@verizon.spam.net> - 2014-08-26 13:39 -0400
  Re: Returning a table in SQL Harry Tuttle <SOZRBLNTLEEE@spammotel.com> - 2014-08-26 21:10 +0200
    Re: Returning a table in SQL Robert Klemme <shortcutter@googlemail.com> - 2014-08-26 22:28 +0200
      Re: Returning a table in SQL Harry Tuttle <SOZRBLNTLEEE@spammotel.com> - 2014-08-26 23:34 +0200
        Re: Returning a table in SQL Robert Klemme <shortcutter@googlemail.com> - 2014-08-27 08:36 +0200
    Re: Returning a table in SQL "AP" <unixpronospam@verizon.net> - 2014-08-27 16:37 -0400
      Re: Returning a table in SQL Harry Tuttle <SOZRBLNTLEEE@spammotel.com> - 2014-08-28 17:51 +0200
        Re: Returning a table in SQL Robert Klemme <shortcutter@googlemail.com> - 2014-08-28 21:45 +0200
        Re: Returning a table in SQL Jasen Betts <jasen@xnet.co.nz> - 2014-08-30 05:45 +0000
        Re: Returning a table in SQL "AP" <unixpronospam@verizon.net> - 2014-09-01 03:02 -0400
          Re: Returning a table in SQL Jasen Betts <jasen@xnet.co.nz> - 2014-09-01 10:56 +0000
            Re: Returning a table in SQL "AP" <unixpronospam@verizon.net> - 2014-09-04 02:57 -0400
              Re: Returning a table in SQL Jasen Betts <jasen@xnet.co.nz> - 2014-09-04 11:21 +0000
  Re: Returning a table in SQL Lennart Jonsson <erik.lennart.jonsson@gmail.com> - 2014-08-27 19:33 +0200

csiph-web