> Having the
> ability to organize tables, indices, etc into tablespaces, and then
> distributing the datafiles in some quasi intelligent fashion is truly pretty
> powerful.
Great feedback! Everyone will agree that there is no problem with the
overall goal. We're just working out the details, and
Thomas Lockhart writes:
> So pg_location would hold the full path (absolute or logical) to every
> file resource in every database? Or would it hold only a list of
> allowed paths? Or only a list of resources for each database (~1 row
> per database) and then table-specific info would be store
I've worked with various versions of Oracle for several years and can share
some of my experiences with their "system catalog" implementation.
They use a fairly simple design in which a database instance consists of 1
.. n tablespaces (that can contain any type of database object) which in
turn c
Richard J Kuhns <[EMAIL PROTECTED]> writes:
> Now for the question. What's the reason for using this method, as opposed
> to using, say, a system catalog to hold the valid locations? Historical?
> Having to stop and restart the backend so it can re-read its environment
> seems kind of archaic.
Richard J Kuhns wrote:
>
> Could anyone please tell me what I'm doing wrong? I'm sure I'm just
> overlooking something, but what?
>
> ==
>
> moran:/acct$ id
> uid=1007(postgres) gid=1003(postgres) groups=1003(postgres)
> moran:/acct$ export P=/acct/pindybook
first guess is
I think what you need to do is:
$ initlocation $P
^
$ createdb indybook -D $P
^
-Original Message-
From: Richard J Kuhns [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 16, 2000 8:26 AM
To: [EMAIL PROTECTED]
Subject: [GENERAL] Question about databases
