| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Bayet <bayet(at)enseirb(dot)fr> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: How to made available for a database an already installed language on another database ? |
| Date: | 2001-01-17 04:34:43 |
| Message-ID: | 15810.979706083@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Richard Bayet <bayet(at)enseirb(dot)fr> writes:
> And the problem is that they can't add any language support with
> createlang.
> Anytime they tried (for example '$>createlang plpgsql theirdb'), the
> program seemed to "freeze" on authentification ...
> They got a :
> "$> createlang plpgsql theirdb
> Password: THEIRPASS Password: THEIRPASS Password: THEIRPASS"
They just needed to be a little more patient ;-) IIRC, the createlang
script invokes psql four or five times, so if you are using password
authentication you're going to have to enter the password four or five
times.
I agree, this isn't particularly user-friendly ... but then, password
auth is inherently not user-friendly for something you invoke
frequently. You might want to look at the other auth methods.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Bayet | 2001-01-17 11:49:01 | Re: How to made available for a database an already installed language on another database ? |
| Previous Message | Richard Bayet | 2001-01-17 03:48:08 | Re: How to made available for a database ... OUPS FORGOTTEN SOMETHING |