Postgres Pro
Downloads
Home   >   mailing lists

Re: interperting type oid in C code - Mailing list pgsql-general

From Ken Been
Subject Re: interperting type oid in C code
Date
Msg-id CANe84ryxstACxng+XkA1N=T9bDiyECw+iniKukt6gA0RsmxjPg@mail.gmail.com
Whole thread Raw
In response to Re: interperting type oid in C code  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-general
Tree view
Well, it's a few types, but the logic is different for each one, so they have to be handled independently anyway.

On Mon, Oct 19, 2015 at 7:40 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Ken Been wrote:
> Those are more complicated, and it's not obvious to me how to use them.  I
> really think that all I need is something as simple as "if (my_oid ==
> INT4OID) {...}".  Is there any reason why I shouldn't just do that?

I don't know.  I was thinking that you might want to handle a larger set
of type OIDs.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: interperting type oid in C code
Next
From: Josip Rodin
Date:
Subject: Re: ERROR: tablespace "archive2" is not empty