Forum OpenACS Q&A: Importing Data: ctl files
Ok, we've already got Oracle 8: The Complete Reference by Koch and Loney. It's now time for PostgreSQL 7: The Complete Reference by Adida and Baccus
Actually, Postgres documentation's not bad. It's just a bit sparse and not always 100% up-to-date. You can read about the COPY command, used in the load-geo-tables script, in the Postgres user's guide.
Postgress has an pg_dump utility wich can be used to dump an entire database (both db structure and content), as a file containing sql commands.
If the ACS/pg team already has an initialised postgress database, with all structure and config data initialised, is simple for them to run pg_dump, then include the dumped file in the ACS/pg distribution.
Then to install it we'll need only to run this sql script against our postgres server in order to initialise the ACS/pg database.
Now that we have installation instructions, this question's obsolete as the instructions tell you how to run the two install scripts.
The problem with pg_dump output is that it is kinda unreadable, spewed forth in a legal but obtuse format that includes a lot of redundant information (emitted to minimize the amount of bookeeping work done by pg_dump, it is easier to dump everything that other tables might need to reference rather than just the stuff actually used).
So we'd need to distribute the "clean", human-formatted and commented datamodel anyway.
Because of these reasons, I don't see any benefit to distributing a dump rather than the two initialization scripts - now that we have documentation!