Re: Big 7.1 open items

At 10:35 20/06/00 -0400, Bruce Momjian wrote:
>>
>> If these are true, then why not create a utility (eg. pg_update_symlinks)
>> that creates the relevant symlinks. It does not matter if they are
>> outdated, from an integrity point of view, and for the most part they can
>> be automatically maintained. Internally, postgresql can totally ignore
them.
>>
>I am a little confused. Are you suggesting that the entire symlink
>thing can be done outside the database? Yes, that is true if we don't
>store the symlink locations in the database. Of course, the database
>has to be down to do this.

The idea was to have postgresql, internally, totally ignore symlinks - use
OID or whatever is technically best for file names. Then create a
utility/command to make human-centric symlinks in a known location. The
symlinks *could* be updated automatically by postgres, if possible, but
would never be used internally. Things like vacuum could report out of date
symlinks, and maybe fix them (but probably not).

It may sound crude, but the only reason for the symlinks is for humans to
'see what is going on', and in most cases they wont be very volatile.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/