From: | Ishaya Bhatt <ishayabhatt(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Datatyp of a column |
Date: | 2013-11-11 14:49:58 |
Message-ID: | CA+E1M321tKzStUui1yr9ELdKKjG2D84f1-fKfaMsaVGH_hN8Ww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Yes!! Thats exactly what I was looking for !! Thanks :)
On Mon, Nov 11, 2013 at 7:58 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Ishaya Bhatt <ishayabhatt(at)gmail(dot)com> writes:
> > In the sorting code, I need to determine the datatype of my sort
> keys
> > and call some code conditionally based on the datatype. Is there any way
> to
> > determine the datatype of a column from the *backend* PostGreSQL code. is
> > the datatype of the column available in the query plan? Any help on this
> > would be very much appreciated.
>
> You really need to be more specific about where you need this information.
> The "sorting code" certainly knows what datatypes it's working with ---
> for example, in tuplesort.c there's a TupleDesc for the tuples passing
> through the sort, and the column types are available from the per-column
> atttypid fields of that. But it's not clear if that's what you're talking
> about.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-11-11 15:26:18 | Re: pgsql: Fix whitespace issues found by git diff --check, add gitattribut |
Previous Message | Colin 't Hart | 2013-11-11 14:39:01 | Re: TABLE not synonymous with SELECT * FROM? |