Re: SET search_path = value

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
Cc: Erwin Brandstetter <brandstetter(at)falter(dot)at>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: SET search_path = value
Date: 2010-04-21 21:37:32
Message-ID: 4BCF701C.6000706@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Le 21/04/2010 00:24, Guillaume Lelarge a écrit :
> Le 20/04/2010 08:54, Guillaume Lelarge a écrit :
>> Le 20/04/2010 05:28, Euler Taveira de Oliveira a écrit :
>>> Guillaume Lelarge escreveu:
>>>> pgAdmin shouldn't use quotes on some parameters: search_path,
>>>> temp_tablespaces. Perhaps others. I don't find a way to pick them
>>>> automatically. For example, their vartype are "string". Which is quite
>>>> ambiguous with others "string" parameters like archive_command. Of
>>>> course, we can use a specific code for them. It would be really easy,
>>>> but I would prefer to find another way.
>>>>
>>> I don't see an easy way. :( Perhaps the plan could be map all of these
>>> parameters (because in the future legacy versions will use this code path) and
>>> then implement a way to identify those strings without quotes in PostgreSQL.
>>
>> Yeah, I don't find a better way to fix this right now.
>>
>
> Fix commited for 1.10. Still needs to work on the trunk patch. Will do
> tomorrow.
>

Fixed in trunk too, with another issue.

--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message svn 2010-04-22 08:45:55 SVN Commit by dpage: r8291 - trunk/pgadmin3/pgadmin/include
Previous Message pgAdmin Trac 2010-04-21 21:36:38 Re: [pgAdmin III] #169: SET search_path = value