Tom Lane wrote:
This is actually in direct contradiction to the original intent of the
plugins/ subdirectory, which was that it only contain libraries that the
local administrator had decided to consider safe and put there manually.
Since the normal superuser-only restrictions for library loading
build process.Thanks.
> To: alvhe...@commandprompt.com
> CC: anaeem...@hotmail.com; robertmh...@gmail.com; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] PLUGINS Functionlity in Win32 build scripts
> Date: Thu, 18 Dec 2008 15:43:19 -0500
> From: t...@sss.pgh.pa.us
>
> A
Alvaro Herrera writes:
> Tom Lane escribió:
>> This is actually in direct contradiction to the original intent of the
>> plugins/ subdirectory, which was that it only contain libraries that the
>> local administrator had decided to consider safe and put there manually.
> I think this is fantasy -
Tom Lane escribió:
> AFAICT, the idea of this patch is to make shared libraries that
> automatically install in $libdir/plugins/ rather than $libdir/.
>
> This is actually in direct contradiction to the original intent of the
> plugins/ subdirectory, which was that it only contain libraries that
MUHAMMAD ASIF writes:
> Purpose of this Plugins change is to add support in postgresql source
> to build plugin and install in (install dir)/lib/plugins. We made
> these changes for a plugin module i.e. pldebugger and we found this a
> useful feature that can help postgresql in adding plugins easi
are some other steps involved to build pldebugger on linux and windows if
you like I can send you the more details on that. Thanks.
> From: anaeem...@hotmail.com
> To: robertmh...@gmail.com
> CC: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] PLUGINS Functionlity in Win32 b
I am on it , I understand your concern. I will send you the sample code and
pldebugger details to test the logic ASAP .Thanks.> Date: Tue, 9 Dec 2008
23:36:42 -0500> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]> Subject: Re:
[HACKERS] PLUGINS Functionlity in Win32 build scripts
>> I've been assigned to review this patch, but I confess I'm a little
>> murky on what problem it's trying to solve. Can you explain what I
>> need to do to recreate the problem?
> In postgreSQL, Plugin modules should be installed in (Installation
> dir)lib/plugins to run properly. There is logic
> I've been assigned to review this patch, but I confess I'm a little
> murky on what problem it's trying to solve. Can you explain what I
> need to do to recreate the problem?
>
> There's also this comment on the Wiki (not sure why it wasn't posted
> to the mailing list...): "Dave Page says: This
On Tue, Sep 9, 2008 at 3:04 AM, MUHAMMAD ASIF <[EMAIL PROTECTED]> wrote:
> I am currently working in EnterpriseDB (www.enterprisedb.com). During
> the integration of pldebugger ( http://pgfoundry.org/projects/edb-debugger )
> with postgres on windows I faced a problem that plugins are not b
Please checkout the patch that adds the PLUGINS functionality in
src/makefiles/pgxs.mk it covers the Unix side of functionality. Thanks.
> Date: Sat, 13 Sep 2008 10:33:30 +0300
> To: [EMAIL PROTECTED]
> CC: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] PLUGINS Functionl
MUHAMMAD ASIF wrote:
During the integration of pldebugger (
http://pgfoundry.org/projects/edb-debugger ) with postgres on windows I faced
a problem that plugins are not being copied to the lib/plugins directory.
Plugins should be copied in (Installation dir)lib/plugins to work properly.
To so
Hi,
I am currently working in EnterpriseDB (www.enterprisedb.com). During the
integration of pldebugger ( http://pgfoundry.org/projects/edb-debugger ) with
postgres on windows I faced a problem that plugins are not being copied to the
lib/plugins directory. Plugins should be copied in (
13 matches
Mail list logo
