Re: Executing stored procs

On Wed, Jan 15, 2020 at 7:37 AM Anthony Waye <anthony(dot)waye(at)arq(dot)group> wrote:

> Essentially results in a SQL query of: CALL
> "stg_customervip"."sp_stg_customer"(37::bigint, '2020-01-15
> 05:52:31'::timestamp)
>
> If I take that query and run it directly in redshift it runs successfully
> but via psycopg2 it returns:
>
>
>
> psycopg2.errors.FeatureNotSupported: TRUNCATE cannot be invoked from a
> procedure that is executing in an atomic context.
>
> HINT: Try calling the procedure as a top-level call i.e. not from within
> an explicit transaction block. Or, if this procedure (or one of its
> ancestors in the call chain) was created with SET config options, recreate
> the procedure without them.
>
> CONTEXT: SQL statement "TRUNCATE table stg_customervip.Customer"
>
>
>
> While that error sounds legitimate I think it might be a redherring
> because it does execute successfully if I do it manually against redshift.
>

Probably if you run it manually you do it outside a transaction. Psycopg
starts a transaction automatically (no, I don't think it's a good idea, but
it's part of the specs)

http://initd.org/psycopg/docs/usage.html#transactions-control

Try setting `redshift_conn.autocommit = True` after connection creation,
and do without the `commit()`s.

-- Daniele

>