addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1linklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Re: [postgresql-1] 1337 h4x0ring for Fun and Profit(TM)

From: Greg S.
Sent on: Thursday, August 12, 2010 5:23 PM
Igor Polishchuk wrote:
There are several ways to obtain the source tree. Occasional developers can just get the most recent source tree snapshot from ftp://ftp.postgresql.org/pub/snapshot/dev.
If I'm using a snapshot, I need to get a new one every day, is it right?
It might be nice to add a link to a document describing for newbies how to get the source from git.

The two documents you are looking for are http://wiki.postgresql.org/wiki/Working_with_Git and http://wiki.postgresql.org/wiki/Working_with_CVS

They may be more complicated than what you want for those new to the process, but all of the basic details are there too.

If you really want to streamline the whole build environment process, I've built a tool just for that purpose; here's two intros and the code:

http://archives.postgresql.org/pgsql-rrreviewers/2009-11/msg00025.php
http://notemagnet.blogspot.com/2009/12/testing-postgresql-85-alpha3-with-peg.html
http://github.com/gregs1104/peg/

This is what I use to do all my patch review, and it takes care of most of the git repo interaction, directory tree setup, and compile options stuff for you in its default configuration.  You really want to be building patches for review in a private directory tree and then putting that private build into the front of your PATH while testing.  It's really easy to end up testing a mix of the system PostgreSQL and the one you just built otherwise.  peg takes care of all that for you.

-- 
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
[address removed]   www.2ndQuadrant.us

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy