printing oid with %d

Started by Justin Pryzbyover 5 years ago4 messageshackers
Jump to latest
#1Justin Pryzby
pryzby@telsasoft.com
+JsonEncodeDateTime(char *buf, Datum value, Oid typid)
...
+                       elog(ERROR, "unknown jsonb value datetime type oid %d", typid);

I think this should be %u.

commit cc4feded0a31d2b732d4ea68613115cb720e624e
Author: Andrew Dunstan <andrew@dunslane.net>
Date: Tue Jan 16 19:07:13 2018 -0500

Centralize json and jsonb handling of datetime types

#2Michael Paquier
michael@paquier.xyz
In reply to: Justin Pryzby (#1)
Re: printing oid with %d

On Mon, Jul 27, 2020 at 08:55:23PM -0500, Justin Pryzby wrote:

+JsonEncodeDateTime(char *buf, Datum value, Oid typid)
...
+                       elog(ERROR, "unknown jsonb value datetime type oid %d", typid);

I think this should be %u.

Good catch. Yep, Oids are unsigned. We don't backpatch such things
usually, do we? Particularly, this one should not be triggerable
normally because no code paths should call JsonEncodeDateTime() with
an unsupported type Oid.
--
Michael

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Michael Paquier (#2)
Re: printing oid with %d

Michael Paquier <michael@paquier.xyz> writes:

Good catch. Yep, Oids are unsigned. We don't backpatch such things
usually, do we? Particularly, this one should not be triggerable
normally because no code paths should call JsonEncodeDateTime() with
an unsupported type Oid.

Yeah, given that it should be an unreachable case, there's likely
no need to back-patch.

regards, tom lane

#4Michael Paquier
michael@paquier.xyz
In reply to: Tom Lane (#3)
Re: printing oid with %d

On Tue, Jul 28, 2020 at 10:35:54AM -0400, Tom Lane wrote:

Yeah, given that it should be an unreachable case, there's likely
no need to back-patch.

Thanks. Fixed on HEAD then.
--
Michael