Closed ionthegeek closed 1 year ago
Not able to reproduce this issue..
localhost:5433 yugabyte@yugabyte=# CREATE ROLE readaccess;
CREATE ROLE
Time: 109.123 ms
localhost:5433 yugabyte@yugabyte=# GRANT CONNECT ON DATABASE db1 TO readaccess;
GRANT
Time: 67.200 ms
localhost:5433 yugabyte@yugabyte=# GRANT CONNECT ON DATABASE db2 TO readaccess;
GRANT
Time: 72.415 ms
localhost:5433 yugabyte@yugabyte=# GRANT CONNECT ON DATABASE db3 TO readaccess;
GRANT
Time: 108.266 ms
localhost:5433 yugabyte@yugabyte=# GRANT USAGE ON SCHEMA public TO readaccess;
GRANT
Time: 66.294 ms
localhost:5433 yugabyte@yugabyte=# GRANT SELECT ON ALL TABLES IN SCHEMA public TO readaccess;
GRANT
Time: 388.310 ms
localhost:5433 yugabyte@yugabyte=# CREATE USER test WITH PASSWORD 'pass';
CREATE ROLE
Time: 83.435 ms
localhost:5433 yugabyte@yugabyte=# GRANT readaccess TO test;
GRANT ROLE
Time: 83.039 ms
localhost:5433 yugabyte@yugabyte=# ALTER ROLE test set statement_timeout = 0;
ALTER ROLE
Time: 94.247 ms
Jira Link: DB-925
Description
This crash is similar to Issue #6317 but found in version 2.4.4. This version includes the fix for this issue, so there is likely some other code path where we're not setting
attrmiss = NULL;
.The postgres process on the affected system crashed after a series of DDLs.
version:
Application fingerprint: version 2.4.4.0 build 7 revision 5089f374d19429108c505d1b0fb89ec9e068f965 build_type RELEASE built at 20 May 2021 00:40:26 UTCCore backtrace:
Postgres log from this session:
The complete Postgres log has sensitive data in it but I can make it available directly. There were a number of statement timeouts and RPC timeouts happening at the time and the system was also under heavy I/O load. It's not clear if these were contributing factors.
The following DDLs were run just prior to the crash (some sensitive info redacted):
Additional core info - the
tupdesc->constr
structure is itself valid but has invalidcheck
andmissing
values: