pg.ddx.io postgres@postgres.berkeley.edu mailing list archivehelp / color / mirror / Atom feed
source code 2+ messages / 2 participants [nested] [flat]
* source code @ 1993-04-27 22:35 Sean.Levy@cs.cmu.edu 0 siblings, 0 replies; 2+ messages in thread From: Sean.Levy@cs.cmu.edu @ 1993-04-27 22:35 UTC (permalink / raw) To: postgres@postgres.berkeley.edu I'd like to pick up the latest source code for postgres 4.1, since I need to port it to a buncha stuff (alpha/osf1, hp, etc). The situation on postgres.berkeley.edu is a little confusing. After grabbing/unpacking most of what was in pub/postgres/post-pieces/developer/*, I got an error -- zcat complained stdin was corrupted. It looked like I got most of the tree, so I started rooting around, and began to get the sneaking suspicion that the code/docs I was looking at were pretty old (the RCS date stamps on some of the files were from 1991). To add to my consternation, the README seems to indicate this is v4r0r1, not v4r1. Is this true? If so, where can I get the latest stuff? Finally, is there a master list of ports that have been done? I did a port of libpq to AIX 3.1.5 a looong time ago, and have not kept up since then... TIA, -- Sean -- Sean Levy, n-dim Group, EDRC, CMU, 5000 Forbes Ave, PGH, PA 15213 Email: snl+@cmu.edu, Phone: +1 412 268 5221, Fax: +1 412 268 5229 ^ permalink raw reply [nested|flat] 2+ messages in thread
* source code @ 1993-05-18 14:18 M92 <hamiltop@computer-science.manchester.ac.uk> 0 siblings, 0 replies; 2+ messages in thread From: M92 @ 1993-05-18 14:18 UTC (permalink / raw) To: postgres@postgres.berkeley.edu I am involved in a project to set-up a database of objects which will be used in a simulation environment. These objects will consist of various components, including icon bitmap, text and source code (written in C), and will be organised in an inheritance hierarchy. I am investigating how such objects could be established in postgres and of particular concern is how the source code will be stored. In the Stonebraker and Rowe paper The Design of Postgres the type "cproc" is mention, however this is not discussed in the postgres reference manual - has this feature been implemented and if so would it be useful for this application? Two options are being considered : 1. Store the code as a large object. Therefore database integrity and caching and locking issues will be handled by postgres. 2. The source code will be a UNIX file referenced in the object relation. With this option integrity, caching and locking strategies must implemented. I would like to hear form anybody who has attempted to included source code in a postgres database by either these methods,or any other, and anybody who can offer helpful advice on this project. Paul. ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1993-05-18 14:18 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 1993-04-27 22:35 source code Sean.Levy@cs.cmu.edu 1993-05-18 14:18 source code M92 <hamiltop@computer-science.manchester.ac.uk>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox