pg-migrator - src: Add support for specifying port numbers.
Log Message:
-----------
Add support for specifying port numbers.
Modified Files:
--------------
src:
TODO (r1.13 -> r1.14)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pg-migrator/src/TODO.diff?r1=1.13&r2=1.14)
pg_migrator.c (r1.34 -> r1.35)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pg-migrator/src/pg_migrator.c.diff?r1=1.34&r2=1.35)
User Bmomjian wrote:
Log Message:
-----------
Add support for specifying port numbers.
Hmm, I suppose we can't readily run pg_dump against a stand-alone backend?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Heikki Linnakangas wrote:
User Bmomjian wrote:
Log Message:
-----------
Add support for specifying port numbers.Hmm, I suppose we can't readily run pg_dump against a stand-alone backend?
I am confused by the question; we used to default to the 5432 port
numbers.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Bruce Momjian wrote:
Heikki Linnakangas wrote:
User Bmomjian wrote:
Log Message:
-----------
Add support for specifying port numbers.Hmm, I suppose we can't readily run pg_dump against a stand-alone backend?
I am confused by the question; we used to default to the 5432 port
numbers.
I was thinking that we could sidestep the whole port number question if
we didn't try to start up postmaster, and used a stand-alone backend (
postgres --single) instead.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Heikki Linnakangas wrote:
Bruce Momjian wrote:
Heikki Linnakangas wrote:
User Bmomjian wrote:
Log Message:
-----------
Add support for specifying port numbers.Hmm, I suppose we can't readily run pg_dump against a stand-alone backend?
I am confused by the question; we used to default to the 5432 port
numbers.I was thinking that we could sidestep the whole port number question if
we didn't try to start up postmaster, and used a stand-alone backend (
postgres --single) instead.
Libpq can't connect to a stand-alone backend and we have many libpq
queries.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
I was thinking that we could sidestep the whole port number question if
we didn't try to start up postmaster, and used a stand-alone backend (
postgres --single) instead.
That would be a good place to get to eventually, but I think it'd be
a serious error to be expending development effort on the point right
now. We need a *working* migrator; simplifying its use can come later.
regards, tom lane
Tom Lane wrote:
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
I was thinking that we could sidestep the whole port number question if
we didn't try to start up postmaster, and used a stand-alone backend (
postgres --single) instead.That would be a good place to get to eventually, but I think it'd be
a serious error to be expending development effort on the point right
now. We need a *working* migrator; simplifying its use can come later.
And I will have it working for 8.4, if it doesn't already work (I am not
sure).
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +