Hi all,
not sure if I should send it here; if it was reported before in
pgsql-general. you can just ignore it :-)
with postgres 8.2.4:
create table test (t1 text);
create function row2text(test) returns text as 'select $1::text' language
sql immutable;
create index test_row2text_idx on test(
On Thu, Nov 6, 2008 at 08:37, Alex Hunsaker bada...@gmail.com wrote:
On Thu, Nov 6, 2008 at 06:41, Tom Lane t...@sss.pgh.pa.us wrote:
Alex Hunsaker bada...@gmail.com writes:
On Wed, Nov 5, 2008 at 18:03, Andrew Gierth and...@tao11.riddles.org.uk
wrote:
Then explain why the problem goes away
Craig Ringer cr...@postnewspapers.com.au writes:
On 11/01/2010 10:27 PM, Filip RembiaÅkowski wrote:
ERROR: table row type and query-specified row type do not match
DETAIL: Physical storage mismatch on dropped attribute at ordinal
position 2.
I'm pretty certain that's not a bug.
No, it is
On Mon, Jan 11, 2010 at 11:41 AM, Steve White swh...@aip.de wrote:
I see nothing in the documentation about this
http://www.postgresql.org/docs/8.4/static/plpython.html
It only talks about passing composite types into and out of functions.
This is an unpleasant discovery for those
