On Sat, Nov 16, 2002 at 02:11:58PM -0500, Hugh Esco wrote:
> Hey folks:
>
> I've copied the shell dialogue below.
> Everything in: /usr/lib/postgresql/bin is owned by root:root.
It's default instalation in Debian Woody and it works fine
> >postgres@biko:/home/hesco$ psql
> >env: /usr/lib/postgres
Hugh Esco <[EMAIL PROTECTED]> writes:
>> postgres@biko:/home/hesco$ psql
>> env: /usr/lib/postgresql/bin/readpgenv: Permission denied
>> No database specified
>> postgres@biko:/home/hesco$ psql ggp_test
>> env: /usr/lib/postgresql/bin/readpgenv: Permission denied
>> Could not execv /usr/lib/postgre
My existing tree implementation reflects the files contained on disk. The
full pathname to a particlar file is obtained from the path to the parent
directory. I am now considering putting this information into a field in
the table.
Attached you will find the pg_dump from my test database (2.4k)
> You seem to have a very bizarre setup there --- there is no such thing
> as "readpgenv" in the standard Postgres distribution, and
> /usr/lib/postgresql/bin/ isn't the standard place to put the executable
> files either. Perhaps the above is normal for the Debian package of
> Postgres, but I'm a
Dan,
> My existing tree implementation reflects the files contained on disk.
> The
> full pathname to a particlar file is obtained from the path to the
> parent
> directory. I am now considering putting this information into a
> field in
> the table.
> Suggestions, comment, open ridicule, most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message
Instead of storing the path in each row, why not let Postgres
take care of computing it with a function? Then make a view
and you've got the same table, without all the triggers.
CREATE TABLE t
Hi all(s)...
Eu não sou confiável, no entanto, posso confiar no
POSTGRES ???
Silvio
2000info
