Re: Migrating an application with Oracle temporary tables

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Mark Zellers <markz(at)adaptiveinsights(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Migrating an application with Oracle temporary tables
Date: 2019-05-13 20:00:48
Message-ID: CAHOFxGptOKXxnvm7KgopfaXvzdbyJH0W6ziD5cQ6a2VZP0r=LA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

*I did find a scenario where this approach does run into trouble. That is,
if the function/procedure is executed against the permanent table and then
you go to run it against a temporary table. In that case, I do get the
wrong answer, and I haven't yet figured out how to reset that without
dropping the procedure and re-defining it. For my purposes, that is "good
enough" -- I can promise not to run such procedures against the temporary
table.*

You may want to be explicit and refer to the table with schema like *select
* from public.table_name *OR* select * from pg_temp.table_name *to avoid
confusion caused by the default behavior of using the temp table if it
exists.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-05-13 20:10:10 Re: does postgresql backup require additional space on disk
Previous Message Julie Nishimura 2019-05-13 19:33:58 Re: does postgresql backup require additional space on disk