Re: Add notification on BEGIN ATOMIC SQL functions using temp relations - Mailing list pgsql-hackers

From Bernice Southey
Subject Re: Add notification on BEGIN ATOMIC SQL functions using temp relations
Date
Msg-id CAEDh4nxXYxbPQQiHBUY6pg3cFxbUKQFdERQ_i6EqDhUm=-Ksyg@mail.gmail.com
Whole thread Raw
In response to Re: Add notification on BEGIN ATOMIC SQL functions using temp relations  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:
>if a temp table is used to
> define an old-style function's argument or result type, eg
>         create function get_mytable() returns setof mytable as ...
> This is problematic because the function will go away when mytable
> does, no matter how its body is expressed.
I briefly did try using my temp table as the result type and was
delighted I could, but my client library wasn't. I had no idea I'd
accidentally made my functions weirdly temporary, so your notice would
have been very useful.

Thanks, Bernice



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: pgsql: Teach DSM registry to ERROR if attaching to an uninitialized ent
Next
From: Nathan Bossart
Date:
Subject: Re: another autovacuum scheduling thread