From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Arnold, Sandra *EXTERN*" <ArnoldS(at)osti(dot)gov>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Substitutes for some Oracle packages |
Date: | 2009-09-18 07:04:06 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C203937F20@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sandra Arnold wrote:
> We are in the process of migrating from Oracle to PostgreSQL.
> One of the things that we are needing to find out is what to
> use in place of Oracle supplied functionality such as
> "DBMS_OUTPUT" and "UTL_FILE". We are currently using this
> type of functionality in Stored Procedures and packages.
> What are the options in PostgreSQL for replacing these two
> packages in a stored procedure/function?
RAISE NOTICE has been mentioned.
Apart from the possibility to write file I/O functions in Perl,
there are some functions that are already included in PostgreSQL:
pg_read_file and pg_stat_file.
The contrib module "adminpack" provides pg_file_write,
pg_file_rename, pg_file_unlink.
Together these are enough for simple file system access,
although they don't provide as much as UTL_FILE.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | el dorado | 2009-09-18 11:17:46 | Re[3]: Problems with pg_dump for PG8.4 for WinXP (MinGW build) |
Previous Message | Peter Eisentraut | 2009-09-18 04:24:14 | Re: PostgreSQL nonstandard use of escape in a string literal |