| 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: | 868B0005-5BE7-11D8-91F4-000A95A0910A@scottg.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
thanks,
/s.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Gibson | 2004-02-10 16:44:02 | Re: [GENERAL] dblink - custom datatypes don't work |
| Previous Message | Tom Lane | 2004-02-10 15:55:41 | Re: [PATCHES] Current-stream read for psql's \copy |