Re: [HACKERS] pgaccess 0.98 - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [HACKERS] pgaccess 0.98
Date
Msg-id 3821A9B7.1FBB1797@alumni.caltech.edu
Whole thread Raw
In response to pgaccess 0.98  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] pgaccess 0.98
List pgsql-hackers
> The tricky part is that pgaccess must know the 'wish' path that is
> determined by configure, and the POSTGRESDIR path which comes from
> Makefile.global, so I had to create a Makefile.in, and a pgaccess.sh.
> Makefile.in is set a configure time, and pgaccess.sh is set at compile
> time.  The final script pgaccess has hardcoded in it the path to wish,
> and the pgaccess directory inside the install directory.

Hmm. There is a common trick to finding wish (and presumably other
"shells") for a shell script; it involves an "exec" as the first
executable line of the script. Did this just recently. I'll look it up
when I get to work.

Your path must of course be set properly; is that not acceptable?
Can't we tolerate minor changes in wish version without
rebuilding/reinstalling from Postgres sources??
                    - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: Performance glitch in GetCurrentAbsoluteTime()
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] sort on huge table