To: c k <shreeseva.learning@gmail.com>
cc: pgsql-general@postgresql.org, pgsql-admin@postgresql.org
Subject: Re: [GENERAL] different results for large objects 
In-reply-to: <d8e7a1e30903170456q767429dt4170f19662fbd2c9@mail.gmail.com> 
References: <d8e7a1e30903170456q767429dt4170f19662fbd2c9@mail.gmail.com>
Comments: In-reply-to c k <shreeseva.learning@gmail.com>
	message dated "Tue, 17 Mar 2009 17:26:44 +0530"
Date: Tue, 17 Mar 2009 08:43:05 -0400
Message-ID: <6995.1237293785@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

c k <shreeseva.learning@gmail.com> writes:
> I am getting correct results with following query i.e. binary objects as
> they are inserted.

> select docimages.* from docimages where docimages.accobjecttype=9 ORDER BY
> docimages.docimagename;

> but when I created a function as follows, binary objects are not shown,

There is no server-side behavior that would cause that query to show you
a large object's contents instead of its identifying number.  I suppose
that you have some client-side code that does something magic when it
sees a result column of type "lo", and that for some reason this code
is not successfully recognizing the case where the column is coming out
of a function.  Since you've shown us neither the troublesome query
nor the client-side code, it's hard to speculate further than that.

			regards, tom lane