| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Restrict allowed database names? |
| Date: | 2010-03-21 17:56:13 |
| Message-ID: | c3a7de1f1003211056uaeb2318yb8effa9ee5cc44d0@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 21 March 2010 20:43, Daniel Verite <daniel(at)manitou-mail(dot)org> wrote:
> Sergey Konoplev wrote:
>
>> What about PL/pgSQL wrapper function for CREATE DATABASE with database
>> name check and SECURITY DEFINER option.
>
> Not possible because CREATE DATABASE can't be executed within a function (nor
> within a transaction).
Ah, exactly. Well than what if we use PL/Python or PL/Perl function
where we do connect to this postgres server and do CREATE DATABASE?
Looks very tricky but seems to be working.
--
Sergey Konoplev
Blog: http://gray-hemp.blogspot.com / Linkedin:
http://ru.linkedin.com/in/grayhemp
JID/GTalk: gray(dot)ru(at)gmail(dot)com / Skype: gray-hemp / ICQ: 29353802
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-03-21 18:02:33 | Re: Restrict allowed database names? |
| Previous Message | Daniel Verite | 2010-03-21 17:43:16 | Re: Restrict allowed database names? |