From: Dimitri Fontaine on
Joe Conway <mail(a)joeconway.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

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: "Greg Sabino Mullane" on

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> (FWIW, my recollection of the original design intention for
> pg_controldata was that it was meant as a troubleshooting tool if the
> database wouldn't start up. I'm somewhat bemused to hear that people
> are trying to use it as part of production scripts. It wasn't meant to
> produce machine-readable output, much less to give values that you could
> rely on with respect to a running server.)

I mostly use it to check on the progress of a PITR slave: just curious,
is there a better/preferred way to get that information?

- --
Greg Sabino Mullane greg(a)turnstep.com
PGP Key: 0x14964AC8 201003091016
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkuWZnAACgkQvJuQZxSWSsiqWgCglhHZ/awR5lSkjPG+yzd05ulz
X6AAn0uvraweuz8pG15OybCyMzgfH3XX
=QI2N
-----END PGP SIGNATURE-----



--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers