From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Assert failed in snprintf.c |
Date: | 2018-10-01 14:48:30 |
Message-ID: | 23503.1538405310@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> writes:
> sqlsmith made it again, attached is the query (run against regression
> database) that makes the assert fail and the backtrace.
> this happens in head only (or at least 11 is fine).
Ah. Looks like the has_column_privilege stuff is incautious about whether
it's handed a valid table OID:
regression=# select has_column_privilege(42::oid, 'z'::text, 'q'::text);
server closed the connection unexpectedly
In older branches I get
regression=# select has_column_privilege(42::oid, 'z'::text, 'q'::text);
ERROR: column "z" of relation "(null)" does not exist
but that's only because glibc's snprintf is forgiving about getting a
NULL pointer for %s. On some other platforms it'd end in SIGSEGV.
Will fix, thanks for report!
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2018-10-01 15:37:01 | Re: Add SKIP LOCKED to VACUUM and ANALYZE |
Previous Message | Peter Eisentraut | 2018-10-01 14:43:09 | Re: automatic restore point |