Skip site navigation (1) Skip section navigation (2)

Re: Patch to psql to allow SEARCH_PATH to be set from env

From: Scott Goodwin <scott(at)scottg(dot)net>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch to psql to allow SEARCH_PATH to be set from env
Date: 2004-02-10 16:38:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
On Feb 10, 2004, at 9:51 AM, Christopher Kings-Lynne wrote:

> I have the feeling it wouldn't have been accepted because it was kind 
> of 'arbitrary'.  It's generally a good idea to ask the -hackers list 
> first if a patch is worth writing before actually writing it ;)

Ah well, it was worth the experience.

On Feb 10, 2004, at 10:30 AM, Tom Lane wrote:

> But I'm not eager to support environment variables for things that can
> be set those ways.  There are a heck of a lot of SET variables --- 
> would
> we want an env var for each one?

I agree; simpler is better and there's already a simple way to do it. 
The environment's polluted enough as it is.



In response to

pgsql-patches by date

Next:From: Mark GibsonDate: 2004-02-10 16:44:02
Subject: Re: [GENERAL] dblink - custom datatypes don't work
Previous:From: Tom LaneDate: 2004-02-10 15:55:41
Subject: Re: [PATCHES] Current-stream read for psql's \copy

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group