sysadminmike

Ok to me thats pointing towards a setup config issue with postgres - double check the user/password and also postgres config allows connection - maybe check postgres logs for any...

Perhaps a permission issue and localhost/127.0.0.1 is missing from pg_hba.conf for the db your using? Postgres logs may be able to point in the right direction.

I think you need to check postgres logs (probably somewhere in /var/log) not the output of daemon.js - postgres should give you some clue as to why its not accepting...

It depends on your server (ie os type & postgres version) so really dont know where your server has postgres setup to log to - you may get some clues...

You should be able to see what ip to set it to from postgres.conf - again i would check postgres logs for any clue as to why you cannot connect...

--- EXTRACT fieldname and fieldtype - where there is only one type of doc - essentially same as looking at the doc but gets in table format: -- show equivelent...

--- EXTRACT fieldname and fieldtype - where there is more than one type of doc show equivelent couchdb map / reduce note this can take a long time to execute...

very low priority

Maybe look at doing something with INSERT/UPDATE/DELETE in the trigger so they are converted into bulk requests with bulk size of 1 - ie emulate the current couch_put and do...

Investigate if postgres function can bypass a trigger if so then modify the node update/insert/delete stuff to use a function instead of calling INSERT/UPDATE/DELETE with from_couch set