On Mon, May 20, 2013 at 8:54 PM, Alvaro Herrera
wrote:
> Hello,
>
> Would you guys please trim the quoted text of the emails you're replying
> to? I understand Gmail is obnoxious w.r.t. quoted text, but this is
> starting to become excessive.
Oops, I didnt notice that. Sorry!
Regards,
Atri
-
Hello,
Would you guys please trim the quoted text of the emails you're replying
to? I understand Gmail is obnoxious w.r.t. quoted text, but this is
starting to become excessive.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Service
Sent from my iPad
On 20-May-2013, at 18:14, Amit Langote wrote:
> Wonder though if this question is better asked in pgsql-novice?
>
> On Mon, May 20, 2013 at 9:23 PM, Amit Langote wrote:
>> Hello,
>>
>> I think a more appropriate question to be asked here would be at what
>> point (in the l
Wonder though if this question is better asked in pgsql-novice?
On Mon, May 20, 2013 at 9:23 PM, Amit Langote wrote:
> Hello,
>
> I think a more appropriate question to be asked here would be at what
> point (in the life of a typical tuple), does a tuple's header contain
> t_datum or otherwise,
Hello,
I think a more appropriate question to be asked here would be at what
point (in the life of a typical tuple), does a tuple's header contain
t_datum or otherwise, which I would also like to be answered.
On Mon, May 20, 2013 at 6:06 PM, Soroosh Sardari
wrote:
> Thanks,
>
> If a tuple const
Thanks,
If a tuple constructed in memory we don't need t_heap. I have another
question,
How make an in-memory tuple?
On Mon, May 20, 2013 at 12:46 PM, Amit Langote wrote:
> Hello,
>
> I think the comment just above the HeapTupleFields struct definition
> has the related details.
>
> /*
> * H
Hello,
I think the comment just above the HeapTupleFields struct definition
has the related details.
/*
* Heap tuple header. To avoid wasting space, the fields should be
* laid out in such a way as to avoid structure padding.
*
* Datums of composite types (row types) share the same general s
