On 7/3/19 9:42 AM, Steve Rogerson wrote:
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@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.
Hmm:
test=> select * from user_passwords ;
ERROR: record type has not been registered
test=> select my_from_local(now());
my_from_local
----------------------------------------------
("2019-07-03 19:29:34.587891",-07:00:00,PDT)
(1 row)
test=> select * from user_passwords ;
name | timestamp | password
------+----------------------------------------------+----------
fred | ("2019-07-03 19:28:07.082895",-07:00:00,PDT) | sdfsdf
(1 row)
Now to figure out why?
Steve
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
