RE: citext, actually probably using extensions

2019-09-23 Thread Kevin Brannen
> From: Morris de Oryx > > Not sure about best practices, but what I'm going is like this: > > * Create a schema named extensions. > * Install extensions in this special schema only. I don't put anything else > in there. > * Put the extensions schema early (left) in the search_path for each role.

Re: citext, actually probably using extensions

2019-09-20 Thread Morris de Oryx
Not sure about best practices, but what I'm going is like this: * Create a schema named extensions. * Install extensions in this special schema only. I don't put anything else in there. * Put the extensions schema early (left) in the search_path for each role. * Grant execute access permissivel

Re: citext, actually probably using extensions

2019-09-20 Thread Rob Sargent
> On Sep 20, 2019, at 1:12 PM, Tom Lane wrote: > > stan writes: >> But I must be doing something wrong. As the PG superuser, I did this: >> postgres=# CREATE EXTENSION IF NOT EXISTS citext WITH SCHEMA public; >> CREATE EXTENSION > >> and as the superuser it shows up in the \dx display > >>

Re: citext, actually probably using extensions

2019-09-20 Thread Tom Lane
stan writes: > But I must be doing something wrong. As the PG superuser, I did this: > postgres=# CREATE EXTENSION IF NOT EXISTS citext WITH SCHEMA public; > CREATE EXTENSION > and as the superuser it shows up in the \dx display > BUT as a normal user: > stan=> \dx > List of installed extension