Re: Status of index location patch
От | Jim Buttafuoco |
---|---|
Тема | Re: Status of index location patch |
Дата | |
Msg-id | 200109151754.f8FHsdB08189@dual.buttafuoco.net обсуждение исходный текст |
Ответ на | Status of index location patch ("Jim Buttafuoco" <jim@buttafuoco.net>) |
Ответы |
Re: Status of index location patch
|
Список | 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 по дате отправления: