Re: machine-readable pg_controldata?

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: machine-readable pg_controldata?
Date: 2010-03-09 10:18:09
Message-ID: 87zl2hbxy6.fsf@hi-media-techno.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> I have not bothered to start a pgfoundry project yet -- thoughts?

For the visibility of the project, pgfoundry is still a good idea it
seems, even if you still have to register separately for the online
catalogue:
http://www.postgresql.org/download/products/1

Now, AFAIUI, if you want to ease the porting of the pgfoundry platform
to something else, the best is not to use much of the features there (if
any), but host the project at github or google code or whatever, and
link from pgfoundry.

For example, I've been switching the code hosting of my extensions from
pgfoundry to github for some time now (switching as soon as maintenance
is needed, git cvsimport is all I need to migrate).

Regards,
--
dim

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2010-03-09 11:10:26 Re: ECPG, two varchars with same name on same line
Previous Message Heikki Linnakangas 2010-03-09 09:56:23 Re: lock mode for ControlFileLock which pg_start_backup uses