Re: Problem with composite type creation in C under Linux - Mailing list pgsql-hackers

From Marios Vodas
Subject Re: Problem with composite type creation in C under Linux
Date
Msg-id AANLkTinG-wk3fBjqgCXPOPgtUdaxZpc5dt72c2v7bB8A@mail.gmail.com
Whole thread Raw
In response to Re: Problem with composite type creation in C under Linux  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Thank you! now I understand it...<br /><br /><div class="gmail_quote">On Wed, Mar 2, 2011 at 7:35 PM, Tom Lane <span
dir="ltr"><<ahref="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span> wrote:<br /><blockquote
class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Marios Vodas
<<ahref="mailto:mvodas@gmail.com">mvodas@gmail.com</a>> writes:<br /> > I have developed some custom composite
andbase types in PostgreSQL 9 which<br /> > you can find in the code I provide below.<br /> > I compile my C
libraryusing GCC 4.5 under Linux and Visual Studio 2010<br /> > under Windows.<br /><br /> > The problem is when
Irun this command: *SELECT to_composite('((1, 2), (3,<br /> > 4))'::m_segment_base)*.<br /> > This is the result
Iget in Windows and Linux respectively:<br /> >     Windows: "("(1,2)","(3,4)")"<br /> >     Linux:
"("(1,)",)"<br/><br /></div>You're passing a single isnull flag to heap_form_tuple calls that are<br /> expecting
arraysof two flags ... and even the one value that's there<br /> according to the code isn't being initialized, so it's
remarkablethat<br /> this code works at all on any platform.<br /><br />                        regards, tom lane<br
/></blockquote></div><br/> 

pgsql-hackers by date:

Previous
From: Nicolas Barbier
Date:
Subject: Re: Native XML
Next
From: Alvaro Herrera
Date:
Subject: WAL segments pile up during standalone mode