Issue with new save-as dialog for postgres

[Phil Longstaff]

On May 18, 2009 10:01:04 pm Phil Longstaff wrote:
> On May 18, 2009 09:33:44 pm Scott Peshak wrote:
> > On Mon, May 18, 2009 at 7:44 PM, Phil Longstaff <plongstaff at rogers.com> 
wrote:
> > > Does anything show up in your gnucash trace file?
> >
> > Yep:
> >
> > * 17:22:14  CRIT <gnc.backend.dbi> [gnc_dbi_postgres_session_begin()]
> > Unable to connect to
> > postgres://postgres.otherhost.local:gnucash:gnucash:password: -2
> > * 17:22:28  CRIT <GLib> g_hash_table_destroy: assertion `hash_table !=
> > NULL' failed
> > * 17:22:42  CRIT <gnc.gui> cb_uri_type_changed_cb: assertion `faw !=
> > NULL' failed
> > * 17:23:10  CRIT <gnc.backend.dbi> [pgsql_error_fn()] DBI error: could
> > not connect to server: Connection refused
> >     Is the server running on host "postgres.otherhost.local" and
> > accepting TCP/IP connections on port 0?
> >
> > I can successfully connect using the psql CLI client from my
> > workstation to that server as the gnucash user, so I'm not sure why
> > this is happening.
>
> Hmm.  I wonder why it is trying port 0?

OK.  I found the problem.  The dbi is specifying port 0.  The default for 
postgres is 5432, so I can easily change it to that.  For a non-default 
installation, I'm not sure how the user should specify the port.

Phil