Re: CREATEDB Where ??
От | Peter Moscatt |
---|---|
Тема | Re: CREATEDB Where ?? |
Дата | |
Msg-id | G8kf7.126970$Xr6.694533@news-server.bigpond.net.au обсуждение исходный текст |
Ответ на | Re: CREATEDB Where ?? (reina@nsi.edu (Tony Reina)) |
Ответы |
Re: Re: CREATEDB Where ??
|
Список | pgsql-hackers |
Thanks Tony... yes that helps explain why I am not seeing what I expected to see. Right..... If I was developing an application, say with Python and I needed to transport my created database and make it part of an installation process (create a tar ball with all needed components), do I just include the /usr/local/pgsql/data directory as part of my dist ?? Pete Tony Reina wrote: > Peter Moscatt <pmoscatt@bigpond.net.au> wrote in message > news:<4x9f7.126086$Xr6.689318@news-server.bigpond.net.au>... >> I am pretty new to PostgreSQL so please bare with me :-) >> >> When issuing the CREATEDB MyDb then creating some tables with CREATE >> TABLE, I then go back and do a search for the file I have just created >> (MyDb) but can't find the physical file. >> >> Does one actually exist ?? >> >> Pete > > Sure it does. The problem you are having is that since the > implementation of TOAST in PG 7.1, all of the db and table names are > represented by numbers in the physical file system > (usr/local/pgsql/data/base). So if you tried to do an 'ls' or 'find' > for the name of your database, it probably wouldn't show up. However, > just do a 'psql {db_name}' (where {db_name} is the name of your > database) and you'll see that everything is kosher. > > To translate the oid numbers to their respective names, use the > oid2name function found in the /contrib under your Postgres source > code. > > -Tony >
В списке pgsql-hackers по дате отправления: