| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Mario Weilguni <mweilguni(at)sime(dot)com> |
| Subject: | Re: Crash in pgCrypto? |
| Date: | 2008-06-16 21:59:18 |
| Message-ID: | 20080616215918.GH4325@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Fetter wrote:
> I, too, would be happy to do the legwork on this one. I believe we'd
> want to have both per-db and per-role settings for search_path.
> What's involved with creating that latter?
I'm not sure what's your point here, but you can already use
ALTER ROLE foo SET search_path=...
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-06-16 22:00:33 | Re: Crash in pgCrypto? |
| Previous Message | David Fetter | 2008-06-16 21:48:45 | Re: Question about Encoding a Custom Type |