You don’t tell us if other users will be concurrently changing any of the
records involved. If you could guarantee that the table won’t be changed, you
might be better off doing a CREATE TABLE table_new as SELECT … FROM table_old,
dropping table_old, and finally renaming table_new. Given the
Just out of curiosity, what kind of trigger are you using, a row level trigger
or a statement level trigger? If you are using a row level trigger, see if you
can achieve your requirements using a statement level trigger instead. I’m
relatively new to Postgres, so there could be some limit that
lbe
Sent: Thursday, May 2, 2019 1:00 AM
To: Mark Zellers ;
pgsql-general@lists.postgresql.org
Subject: Re: Migrating an application with Oracle temporary tables
Mark Zellers wrote:
> One of the issues I have run into in migrating from Oracle to PostgreSQL is
> the difference in tempor
One of the issues I have run into in migrating from Oracle to PostgreSQL is the
difference in temporary table behavior. I've come up with what I think is a
cunning plan, but I wonder if anyone with more PostgreSQL understanding can
shoot holes in it.
Oracle defines their temporary tables stati
