Re: t_natts references in comments

Lists: pgsql-hackers
From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: t_natts references in comments
Date: 2012-03-08 20:33:29
Message-ID: 4F58C3390200002500046057@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

I wasted a few minutes today tracking down what a couple comments
really meant to say. t_natts no longer exists as a separate field;
the equivalent value is now pulled from t_infomask2 using a macro.

Small patch to correct the comments is attached.

-Kevin

Attachment Content-Type Size
t_natts.patch text/plain 1.5 KB

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: t_natts references in comments
Date: 2012-03-09 06:09:30
Message-ID: 4F599E9A.6020308@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 08.03.2012 22:33, Kevin Grittner wrote:
> I wasted a few minutes today tracking down what a couple comments
> really meant to say. t_natts no longer exists as a separate field;
> the equivalent value is now pulled from t_infomask2 using a macro.
>
> Small patch to correct the comments is attached.

Thanks, applied.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com