Re: 7.4 ERROR: CREATE LOCAL TEMPORARY TABLE ... ON COMMIT DROP inside a function

From: "ezra epstein" <ee_newsgroup_post(at)prajnait(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: 7.4 ERROR: CREATE LOCAL TEMPORARY TABLE ... ON COMMIT DROP inside a function
Date: 2004-01-02 15:05:46
Message-ID: PV2dnXpZ_djQGWiiXTWc-g@speakeasy.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Typo, see below:

"ezra epstein" <ee_newsgroup_post(at)prajnait(dot)com> wrote in message
news:xl2dnZZJS71gH2iiXTWc-g(at)speakeasy(dot)net(dot)(dot)(dot)
> I found a post about something similar in an older release:
> http://archives.postgresql.org/pgsql-bugs/2002-08/msg00151.php
>
> Here's the issue. Inside a function I'm calling
> CREATE LOCAL TEMPORARY TABLE ds_copy_item_meta ( LIKE
> merchandise.item_meta EXCLUDING DEFAULTS ) on COMMIT DROP;
>
> Of course it might be that the ON COMMIT DROP is redundant, I don't know
> enough about temp tables. Here's the problem, however, the first call of
> the table works fine. The second call it complains about a bad OID.
Could

that should read: the first call of the function.

> it be that the bug that was fixed for regular temporary tables (without an
> on commit modifier) somehow didn't get fixed for this construct?
>
> The work-around has been to just not use the modifier, but I was surprised
> by the OID error and think it might be incorrect behavior.
>
> == Ezra Epstein.
>
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message ezra epstein 2004-01-02 15:18:45 Any way to have CREATEUSER privs without having all privs?
Previous Message ezra epstein 2004-01-02 15:04:11 Re: 7.4 Alter User xxx VALID UNTIL '2000-01-01' does not work