Re: printing oid with %d

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: printing oid with %d
Date: 2020-07-28 14:35:54
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)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

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Hamid Akhtar 2020-07-28 14:51:15 Re: Rethinking opclass member checks and dependency strength
Previous Message Dmitry Dolgov 2020-07-28 13:43:08 Re: [HACKERS] [PATCH] Generic type subscripting