Re: Status of index location patch - Mailing list pgsql-hackers

From Jim Buttafuoco
Subject Re: Status of index location patch
Date
Msg-id 200109151754.f8FHsdB08189@dual.buttafuoco.net
Whole thread Raw
In response to Status of index location patch  ("Jim Buttafuoco" <jim@buttafuoco.net>)
Responses Re: Status of index location patch
List pgsql-hackers
Vadim,

I guess I am still confused...

In dbcommands.c resolve_alt_dbpath() takes the db oid as a argument. 
This number is used to "find" the directory where the data files live. 
All the patch does is put the indexes into a "db oid"_index directory
instead of "db oid"


This is for tables  snprintf(ret, len, "%s/base/%u", prefix, dboid);
This is for indexes snprintf(ret, len, "%s/base/%u_index", prefix,
dboid);

And in catalog.c
tables: sprintf(path, "%s/base/%u/%u", DataDir, rnode.tblNode,
rnode.relNode);
indexes: sprintf(path, "%s/base/%u_index/%u", DataDir,                               rnode.tblNode,rnode.relNode);

Can you explain how I would get the tblNode for an existing database
index files  if it doesn't have the same OID as the database entry in
pg_databases.

Jim


> > Just wondering what is the status of this patch.  Is seems from
comments
> > that people like the idea.  I have also looked in the archives for
other
> > people looking for this kind of feature and have found alot of
interest.
> > 
> > If you think it is a good idea for 7.2, let me know what needs to be
> > changed and I will work on it this weekend.
> 
> Just change index' dir naming as was already discussed.
> 
> Vadim
> 
> 




pgsql-hackers by date:

Previous
From: Haroldo Stenger
Date:
Subject: [Fwd: [ADMIN] Transaction Aborting on sql call failure]
Next
From: "Vadim Mikheev"
Date:
Subject: Re: Status of index location patch