Re: UUID generation problem

On 10/5/20 9:46 AM, James B. Byrne wrote:
> 
> 
> On Mon, October 5, 2020 12:08, Adrian Klaver wrote:
>> On 10/5/20 8:57 AM, James B. Byrne wrote:
>>>
>>>
>>> On Mon, October 5, 2020 11:15, Adrian Klaver wrote:
>>>>
>>>> Per Tom's post this does not make sense.
>>>>
>>>> What if you connect doing?:
>>>>
>>>> psql --dbname=idempiere --username=idempiere_dbadmin
>>>>
>>>> And specify the port(-p)
>>>>
>>>> Cut out the sudo.
>>>>
>>>>
>>>> Then do:
>>>>
>>>> select current_schemas(true);
>>>>
>>>> select uuid_generate_v4();
>>>>
>>>> select public.uuid_generate_v4();
>>>>
>>>
>>> [root@accounting-2 ~ (master)]# psql --dbname=idempiere
>>> --username=idempiere_dbadmin
>>> Password for user idempiere_dbadmin:
>>> psql (11.8)
>>> Type "help" for help.
>>>
>>> idempiere=# select current_schemas(true);
>>>       current_schemas
>>> ------------------------
>>>    {adempiere,pg_catalog}
>>
>> Well there is your problem. That is a different search_path and it does
>> not include the 'public' schema. This would indicate you are connecting
>> to a different instance of Postgres then in your previous example. I'm
>> going to bet you are connecting to different ports. I use the following
>> in my .psqlrc(local psql conf file):
>>
>> \set PROMPT1 '%/%R%# '
>>
>> to get the database name and port. I would try that at least
>> temporarily(at psql prompt) to sort out what/where you are connecting to.
>>
> 
> [root@accounting-2 ~ (master)]# cat .psqlrc
> \set PROMPT1 '%/%R%# '
> 
> [root@accounting-2 ~ (master)]#  psql --dbname=idempiere
> --username=idempiere_dbadmin --host=localhost
> Password for user idempiere_dbadmin:
> psql (11.8)
> Type "help" for help.
> 
> idempiere=# \set
> . . .
> PROMPT1 = '%/%R%# '
> PROMPT2 = '%/%R%# '
> PROMPT3 = '>> '
> . . .
> VERSION_NAME = '11.8'
> VERSION_NUM = '110008'
> idempiere=#
> idempiere=#
> idempiere=#
> 
> The setting does not appear to alter the actual prompt.

That is because I sent the wrong prompt:( It should have been:

\set PROMPT1 '%/(%>)%R%# '

> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com