[pgAdmin III] #85: Per-function configuration parameters loss

From: "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org>
To:
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: [pgAdmin III] #85: Per-function configuration parameters loss
Date: 2009-10-09 20:16:25
Message-ID: 056.a1787c413af0a02c29435bc3433e2950@code.pgadmin.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

#85: Per-function configuration parameters loss
-----------------------------+----------------------------------------------
Reporter: Dmitry Samokhin | Owner: dpage
Type: bug | Status: new
Priority: minor | Milestone: 1.10.1
Component: pgadmin | Version: 1.10
Keywords: function | Platform:
-----------------------------+----------------------------------------------
When any server configuration parameters (or variables) are set on a per-
function basis, the script displayed in the pgAdmin SQL pane looks like
this:

CREATE OR REPLACE FUNCTION ... ;
ALTER FUNCTION ... SET ...;

If then I edit the function body and save my work, all variables are lost,
since (it can be cheked easily) pgAdmin does not generate neither SET
option in the CREATE OR REPLACE FUNCTION command nor separate ALTER
FUNCTION ... SET ... one.

This is critical since for security reasons functions with the SECURITY
DEFINER option should contain appropriate 'search_path' variable setting.
And now a DB developer/admin has to double-check per-function variables
when editing functions using pgAdmin.

Regards,
Dmitry.

P.S. For 8.3 backend or later pgAdmin might generate the SET option within
CREATE OR REPLACE FUNCTION command for the SQL pane.

--
Ticket URL: <http://code.pgadmin.org/trac/ticket/85>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message pgAdmin Trac 2009-10-09 20:18:05 Re: [pgAdmin III] #85: Per-function configuration parameters loss
Previous Message pgAdmin Trac 2009-10-09 20:14:04 Re: [pgAdmin III] #84: Couple of minor Slony issues