RE: Scripting a ALTER PROCEDURE or FUNCTION to Change OWNER
| От | |
|---|---|
| Тема | RE: Scripting a ALTER PROCEDURE or FUNCTION to Change OWNER |
| Дата | |
| Msg-id | 002f01dac1be$7fab9830$7f02c890$@incisivetechgroup.com обсуждение исходный текст |
| Ответ на | Re: Scripting a ALTER PROCEDURE or FUNCTION to Change OWNER ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Список | pgsql-admin |
I provided the scripts , use , how ever you like
From: David G. Johnston <david.g.johnston@gmail.com>
Sent: Tuesday, June 18, 2024 4:23 PM
To: lennam@incisivetechgroup.com
Cc: PABLO ANDRES IBARRA DUPRAT <Pablo.Ibarra@itau.cl>; pgsql-admin@lists.postgresql.org
Subject: Re: Scripting a ALTER PROCEDURE or FUNCTION to Change OWNER
On Tue, Jun 18, 2024 at 12:58 PM <lennam@incisivetechgroup.com> wrote:
Following scripts will take care to change schema owner
Mk_altr_proc_owner.sql ( copy past this SQL statement)
SELECT ' alter procedure '||rtrim(nspname)||'.'||ltrim( proname )||' owner to targetschema;'
Maybe using quote_ident to prevent, unlikely as it may be, SQL injection issues. The trims seem likely to be unnecessary - catalog contents should be clean.
Psql -h hostname -U ursename -d dbname -t -A -f mk_altr_proc_owner.sql -o altr_proc_owner.sql
The script output file is nice to check one's works I guess. But if you are going to use psql there is the \gexec meta-command that makes this even easier.
David J.
В списке pgsql-admin по дате отправления: