We recently updated our PuppetDB servers to PuppetDB 6.12.0 and PostgreSQL 
12.
Started getting these errors:

ERROR:  relation "resource_events_20200917z" does not exist at character 13
ERROR:  relation "resource_events_20200917z" already exists
ERROR:  deadlock detected
ERROR:  could not serialize access due to concurrent delete

Not sure if it is a PuppetDB setting or a Postgresql issue. Has anyone else 
seen this?

Here is more detail:

2020-09-17 14:32:49.515 UTC [3941] ERROR:  relation 
"resource_events_20200917z" does not exist at character 13
2020-09-17 14:32:49.515 UTC [3941] QUERY:  INSERT INTO 
resource_events_20200917Z SELECT ($1).*
2020-09-17 14:32:49.515 UTC [3941] CONTEXT:  PL/pgSQL function 
resource_events_insert_trigger() line 8 at EXECUTE
2020-09-17 14:32:49.515 UTC [3941] STATEMENT:  INSERT INTO resource_events 
( new_value, property, name, file, report_id, event_hash, old_value, 
containing_class, certname_id, line, resource_type, status, resource_title, 
timestamp, containment_path, message ) VALUES ( $1, $2, $3, $4, $5, $6, $7, 
$8, $9, $10, $11, $12, $13, $14, $15, $16 )
        RETURNING *
2020-09-17 14:32:49.538 UTC [3937] ERROR:  relation 
"resource_events_20200917z" already exists
2020-09-17 14:32:49.538 UTC [3937] STATEMENT:  CREATE TABLE IF NOT EXISTS 
resource_events_20200917Z (CHECK ( "timestamp" >= TIMESTAMP WITH TIME ZONE 
'2020-09-17T00:00:00Z' AND "timestamp" < TIMESTAMP WITH TIME ZONE 
'2020-09-18T00:00:00Z' )) INHERITS (resource_events)
2020-09-17 14:32:49.538 UTC [3945] ERROR:  relation 
"resource_events_20200917z" already exists
2020-09-17 14:32:49.538 UTC [3945] STATEMENT:  CREATE TABLE IF NOT EXISTS 
resource_events_20200917Z (CHECK ( "timestamp" >= TIMESTAMP WITH TIME ZONE 
'2020-09-17T00:00:00Z' AND "timestamp" < TIMESTAMP WITH TIME ZONE 
'2020-09-18T00:00:00Z' )) INHERITS (resource_events)
2020-09-17 14:32:49.538 UTC [3941] ERROR:  relation 
"resource_events_20200917z" already exists
2020-09-17 14:32:49.538 UTC [3941] STATEMENT:  CREATE TABLE IF NOT EXISTS 
resource_events_20200917Z (CHECK ( "timestamp" >= TIMESTAMP WITH TIME ZONE 
'2020-09-17T00:00:00Z' AND "timestamp" < TIMESTAMP WITH TIME ZONE 
'2020-09-18T00:00:00Z' )) INHERITS (resource_events)
2020-09-17 14:33:27.917 UTC [2875] ERROR:  deadlock detected
2020-09-17 14:33:27.917 UTC [2875] DETAIL:  Process 2875 waits for 
AccessExclusiveLock on relation 7883116 of database 16385; blocked by 
process 3945.
        Process 3945 waits for RowExclusiveLock on relation 7883178 of 
database 16385; blocked by process 2875.
        Process 2875: drop table if exists reports_20200917z cascade
        Process 3945: INSERT INTO resource_events ( new_value, property, 
name, file, report_id, event_hash, old_value, containing_class, 
certname_id, line, resource_type, status, resource_title, timestamp, 
containment_path, message ) VALUES ( $1, $2, $3, $4, $5, $6, $7, $8, $9, 
$10, $11, $12, $13, $14, $15, $16 )
        RETURNING *


2020-09-17 14:34:47.339 UTC [2875] ERROR:  could not serialize access due 
to concurrent delete
2020-09-17 14:34:47.339 UTC [2875] STATEMENT:  delete from fact_paths fp  
where not exists (select 1 from tmp_live_paths                      where 
tmp_live_paths.path = fp.path)

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6f23bccd-22cd-48dd-acd8-e8e0247440fdn%40googlegroups.com.

Reply via email to