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

From: Neil Conway <neilc(at)samurai(dot)com>
To: Scott Goodwin <scott(at)scottg(dot)net>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch to psql to allow SEARCH_PATH to be set from env
Date: 2004-02-10 20:24:07
Message-ID: 8765eewumw.fsf@mailbox.samurai.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Scott Goodwin <scott(at)scottg(dot)net> writes:
> If anyone cares to, I'd still like feedback on anything I could have
> done better in this patch

Since, you asked, two minor points: (1) palloc() is for memory
allocation in the backend; use malloc() (or a wrapper like
pg_malloc()) in frontend apps and libpq (2) naming variables like
word1_Word2 is inconsistent with the surrounding code.

-Neil

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Neil Conway 2004-02-10 20:27:31 Re: Patch to psql to allow SEARCH_PATH to be set from env
Previous Message Andrew Sullivan 2004-02-10 18:57:14 Re: [PATCHES] Current-stream read for psql's \copy