Re: BUG #3363: Unable to load a plugin/library using -c switch to the psql

From: Douglas Toltzman <doug(at)oakstreetsoftware(dot)com>
To: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3363: Unable to load a plugin/library using -c switch to the psql
Date: 2007-06-05 17:00:24
Message-ID: 6800FF41-9626-45D2-B53E-FFDCEE257222@oakstreetsoftware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I've not done what you're doing, so this is just a suggestion. I'm
not sure about the Windows shell, but the bash shell will convert
$libdir before handing it off to psql. Is it possible that $libdir
has a different meaning in psql than it does to the shell?

On Jun 5, 2007, at 4:20 PM, Gurjeet Singh wrote:

>
> The following bug has been logged online:
>
> Bug reference: 3363
> Logged by: Gurjeet Singh
> Email address: singh(dot)gurjeet(at)gmail(dot)com
> PostgreSQL version: 8.3devel
> Operating system: Windows
> Description: Unable to load a plugin/library using -c switch
> to the
> psql
> Details:
>
> The following command fails:
>
> psql postgres test -X -c "load '$libdir/plugins/index_adviser.dll';"
>
> Here, 'test' user (non-superuser) is trying to connect to
> 'postgres'
> database, and wishes to load a plugin as the first step.
>
> But if the same 'load' command is fired by the same user after
> log-in
> using psql, then the command succeeds.
>
> postgres=> load '$libdir/plugins/index_adviser.dll';
> NOTICE: IND ADV: Loaded; PID: 1164
> LOAD
> postgres=>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq

Douglas Toltzman
doug(at)oakstreetsoftware(dot)com
(910) 526-5938

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-06-05 17:16:09 Re: BUG #3363: Unable to load a plugin/library using -c switch to the psql
Previous Message Simon Riggs 2007-06-05 16:33:19 Re: BUG #3362: xlog corruption just after initdb on irix