From: | Steve Rogerson <steve(dot)pg(at)yewtc(dot)demon(dot)co(dot)uk> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: postgres 11 issue? |
Date: | 2019-07-03 16:42:28 |
Message-ID: | 6fd9353d-96f5-7114-13cf-f660a581d985@yewtc.demon.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> It seems a bug to me. Can you share an anonymized/simplified definition
> of that table that reproduces the problem?
>
Ok See attached sql set up. I guess you need to to a createdb first.
so :
testdb=# \i db.sql
DROP TRIGGER
DROP TABLE
...
testdb=# select * from user_passwords ;
name | timestamp | password
------+-----------+----------
(0 rows)
testdb=# insert into users (name, password) values ('fred', 'sdfsdf');
INSERT 0 1
testdb=# select * from user_passwords ;
name | timestamp | password
------+---------------------------------------------+----------
fred | ("2019-07-03 16:37:07.124207",01:00:00,BST) | sdfsdf
(1 row)
testdb=# \q
steve(at)work-hp pg_prob$ psql testdb
psql (11.3)
Type "help" for help.
testdb=# select * from user_passwords ;
ERROR: record type has not been registered
Same thing (record type has not been registered/) in a different session that
previously showed user_passwords to be empty in the "normal" way. before the
insert.
It's taken me a while to get this to get it to go wrong and I don't think that
all the complexity is needed, but this at least is consistent.
Steve
Attachment | Content-Type | Size |
---|---|---|
db.sql | application/sql | 2.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-07-03 19:32:00 | Re: postgres 11 issue? |
Previous Message | Marllius | 2019-07-03 16:40:05 | Re: Error updating column of type text as boolean type |