Re: UUID generation problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: byrnejb(at)harte-lyne(dot)ca
Cc: "Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: UUID generation problem
Date: 2020-10-05 16:06:56
Message-ID: 1732745.1601914016@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"James B. Byrne" <byrnejb(at)harte-lyne(dot)ca> writes:
> On Mon, October 5, 2020 10:53, Tom Lane wrote:
>> I continue to suspect that you are somehow
>> confusing yourself by testing in different databases and/or
>> with different user accounts.

> Possibly. I do not make any definitive claims at this point. However, the
> application properties of the DB connection are:

> Connection=xyzCConnection[name\=accounting.harte-lyne.ca
> {localhost-idempiere-idempiere_dbadmin},
> AppsHost\=accounting.harte-lyne.ca,
> WebPort\=8080,
> SSLPort\=8443,
> type\=PostgreSQL,
> DBhost\=localhost,
> DBport\=5432,
> DBname\=idempiere,
> BQ\=false,
> FW\=false,
> FWhost\=,
> FWport\=0,
> UID\=idempiere_dbadmin,
> PWD\=xxxxxxxxxxxxxxxx]

Hm, is "UID" really how they spell "database user name"? Doesn't seem
terribly consistent with the other field names you show here.

> [root(at)accounting-2 ~ (master)]# psql --dbname=idempiere
> --username=idempiere_dbadmin

psql, by default, is going to try to connect to a Unix socket.
I wonder if you've got two postmasters on that machine and the
other one is what's answering TCP port 5432. You might try
explicitly saying "--host=localhost" here.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-10-05 16:08:07 Re: UUID generation problem
Previous Message Tom Lane 2020-10-05 16:01:08 Re: How to execute the sql file in PSQL