From: Chris A. <ro...@gm...> - 2011-09-30 05:49:17
|
Greetings! I'm attempting to set up a test "cluster" on a single computer, for testing purposes. It's the first experience I have with PostgreSQL-XC, and I know I've mucked stuff up, but I'm hoping someone can help me sort out the mess I've got myself into. So far, I've cloned the source tree and configured it --prefix=/usr (this may very well have been an unwise choice). I then created two data directories at /usr/local/pgsql/data and /usr/local/pgsql/data1, and attempted to launch the three parts of the server, in separate windows. All three sessions are running on the same computer (a Dell laptop running 64-bit Ubuntu 10.10), and are invoked from 'sudo su postgres' to get to the expected user. $ gtm -D /usr/local/pgsql/data/gtm/ -p 6667 -l gtm.log & $ tail -F /usr/local/pgsql/data/gtm/gtm.log $ postgres -D /usr/local/pgsql/data -p 15432 -i -X $ postgres -D /usr/local/pgsql/data1 -i -C The command lines were partly derived from http://sourceforge.net/mailarchive/message.php?msg_id=26377904 but I don't really know what port numbers I should use. In /usr/local/pgsql/data/postgresql.conf are a number of references to 'port', most of them commented; the only one that's active is: gtm_port 6667 When I tried to fire up gtm on port 6666, it immediately terminated without message. I assume this means that it couldn't bind to the port, but I have no way to confirm this. There's a similar conf file in .../data1/ which I have now also edited to put gtm_port to 6667. Without this change, I was getting total inability to connect; now, I still get a lack of pooled commections. $ sudo su postgres $ psql psql (9.1beta2) Type "help" for help. postgres=# create user chris with password 'chris'; ERROR: Failed to get pooled connections PANIC: cannot abort transaction 45, it was already committed server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !> Meanwhile, the other logs show odd messages; mainly, complaining that the database was improperly shut down. Any assistance would be much appreciated! Chris Angelico |