Thread: BUG #17535: postgresql-14-orafce 3.22.0-1.pgdg110+1 fails; 3.21.1-1.pgdg110+1 works.
BUG #17535: postgresql-14-orafce 3.22.0-1.pgdg110+1 fails; 3.21.1-1.pgdg110+1 works.
From
PG Bug reporting form
Date:
The following bug has been logged on the website: Bug reference: 17535 Logged by: Dan Ritter Email address: dsr@randomstring.org PostgreSQL version: 14.4 Operating system: Debian bullseye with packaging from apt.postgresql Description: create extension orafce; select trunc(current_timestamp); produces "trunc does not exist" (user did not provide cut-and-paste error, sorry.) Works on 3.21.1-1.pgdg110+1 , does not work on 3.22.0-1.pgdg110+1
Re: BUG #17535: postgresql-14-orafce 3.22.0-1.pgdg110+1 fails; 3.21.1-1.pgdg110+1 works.
From
Pavel Stehule
Date:
pá 1. 7. 2022 v 16:38 odesílatel PG Bug reporting form <noreply@postgresql.org> napsal:
The following bug has been logged on the website:
Bug reference: 17535
Logged by: Dan Ritter
Email address: dsr@randomstring.org
PostgreSQL version: 14.4
Operating system: Debian bullseye with packaging from apt.postgresql
Description:
create extension orafce;
select trunc(current_timestamp);
produces "trunc does not exist" (user did not provide cut-and-paste error,
sorry.)
Works on 3.21.1-1.pgdg110+1 , does not work on 3.22.0-1.pgdg110+1
It is expected
In older releases some functions from orafce extension was in public or pg_catalog schema. It was pretty dirty. Now, all functions are in schema oracle.
please add schema oracle to search_path
like
set search_path to 'orafce, public';
select trunc(current_timestamp);