Re: Possible bug in conversion_create.sql

From: "" <silvio(at)relato(dot)com(dot)br>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Possible bug in conversion_create.sql
Date: 2003-11-04 15:44:39
Message-ID: 1067960679.3fa7c9674b365@webmail.relato.com.br
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>> With the help of two people from #postgresql at irc.freenode.org, I did a
>> initdb -d --pgdata data 2>debug.log and founded out that the problem was
>> that conversion_create.sql wasn't changing $libdir to the actual name

> It's not supposed to. I don't know what problem you had, but this is
> the wrong fix.

I'm sure that sed isn't the correct procedure :-) Somewhere in the way (in the
instalation or in runtime), postgres should change libdir to the actual dir
name, since the error was "no such file or directory"...

But the problem was solved with the change. I'm not a postgres master at all,
so, how postgres knows what to use on the libdir variable? Where the variable
is defined? How I know if this is set?

Thanks for any anwer :-)

Silvio Fonseca
Linux Consultant

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2003-11-04 16:01:04 Re: Possible bug in conversion_create.sql
Previous Message Tom Lane 2003-11-04 15:32:55 Re: rm -rf in initlocation violates Rule of Least Surprise