| From: | Justin Clift <justin(at)postgresql(dot)org> | 
|---|---|
| To: | pmoscatt(at)bigpond(dot)net(dot)au | 
| Cc: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: Re: CREATEDB Where ?? | 
| Date: | 2001-08-20 16:46:23 | 
| Message-ID: | 3B813EDF.50E9B7BC@postgresql.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Hi Pete,
Would it be appropriate to do a SQL dump of the created database via
pg_dump, then reload it during the installation vi psql or the COPY
command?  If you include the whole data/ subdirectory, you'll also get
the WAL logfiles and everything, which you probably don't need.
Of course, you'll need to create a process for updating the *.conf
(postgresql.conf, pg_ident.conf, pg_hba.conf) files correctly too. 
Perl, sed, etc, would all be a starting point here.
Regards and best wishes,
Justin Clift
Peter Moscatt wrote:
> 
> 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
> >
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
-- 
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
   - Indira Gandhi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2001-08-20 16:50:11 | Idea: Worthwhile creating a wrapper script to automate pg_hba.conf entries? | 
| Previous Message | Nicolas Verger | 2001-08-20 16:40:32 | RE: Select parser at runtime .... |