From: | Peter Moscatt <pmoscatt(at)bigpond(dot)net(dot)au> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: CREATEDB Where ?? |
Date: | 2001-08-18 02:10:46 |
Message-ID: | G8kf7.126970$Xr6.694533@news-server.bigpond.net.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)bigpond(dot)net(dot)au> wrote in message
> news:<4x9f7(dot)126086$Xr6(dot)689318(at)news-server(dot)bigpond(dot)net(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Serguei Mokhov | 2001-08-18 03:02:06 | Re: encoding names |
Previous Message | Marc G. Fournier | 2001-08-18 01:51:32 | Re: CVS access lost |