Re: SELECT col INTO TEMP TABLE tab2 ON COMMIT DROP FROM tab1

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Alexander Farber <alexander(dot)farber(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: SELECT col INTO TEMP TABLE tab2 ON COMMIT DROP FROM tab1
Date: 2016-08-12 09:05:33
Message-ID: CA+bJJbx=CM8zzmBSgOwUvfJsQqKrHKb1ohATcAxC4s_rvkaJMA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alexander:

On Fri, Aug 12, 2016 at 11:00 AM, Alexander Farber
<alexander(dot)farber(at)gmail(dot)com> wrote:
> but the custom function I am trying to call (from another function) does not
> return one row, but several rows, which I'd like to store into a temp table:

This I know, I wasn't trying to solve the problem. I was just trying
to point that "select" is not the same in plpgsql and in sql, so you
need to read the docs for plpgsql to find how to solve it.

Francisco Olarte.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris Travers 2016-08-12 09:07:08 Re: Postgres Pain Points 2 ruby / node language drivers
Previous Message Alexander Farber 2016-08-12 09:00:10 Re: SELECT col INTO TEMP TABLE tab2 ON COMMIT DROP FROM tab1