From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Kris Deugau <kdeugau(at)webhart(dot)net>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Database directory names |
Date: | 2002-07-03 16:03:15 |
Message-ID: | 20020703090213.Y7575-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, 3 Jul 2002, Bruce Momjian wrote:
> Stephan Szabo wrote:
> > > Is this a feature, a bug, or a change related to some other critical
> > > functional capability of Postgres? I haven't found anything else that
> > > meets our requirements here, and I can work around this annoyance if
> > > required- but I'd rather be lazy. ;)
> >
> > Switching to numbers for tables and databases helped a few things
> > (including for tables making it easier to rollback a drop table).
> > There's a contrib item, oid2name which will print out a mapping
> > of directory number to database name. The readme gives an example
> > of using it with du.
>
> Uh, actually, only the readme in the current CVS has the example, 7.2.X
> doesn't. I recommend getting oid2name from the snapshot/CVS and using
> that. It has the newer readme and some changes to make the examples
> display properly. Also see the new doc section for 7.3 on disk usage:
>
> http://developer.postgresql.org/docs/postgres/diskusage.html
My bad. I assumed that oid2name wasn't likely to have changed without
actually checking.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-07-03 19:23:34 | Re: Oracle data -> PostgreSQL |
Previous Message | Bruce Momjian | 2002-07-03 15:42:49 | Re: Database directory names |