From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ibrahim Shaame <ishaame@gmail.com>
cc: depesz@depesz.com,
        "pgsql-novice@lists.postgresql.org"
 <pgsql-novice@lists.postgresql.org>
Subject: Re: Adding column in a recursive query
In-reply-to: 
 <CAJOWwD5XcMzwMrkaL-vD8d553y0BzQBppObZhau6zYxA4hj5nw@mail.gmail.com>
References: 
 <CAJOWwD5_saumY5Xv1QAQ=VxwMQrz-tF6G-Fwek-ew52-=_uOXg@mail.gmail.com>
 <acppj9U8zquc2O7z@depesz.com>
 <CAJOWwD5XcMzwMrkaL-vD8d553y0BzQBppObZhau6zYxA4hj5nw@mail.gmail.com>
Comments: In-reply-to Ibrahim Shaame <ishaame@gmail.com>
	message dated "Mon, 30 Mar 2026 17:22:53 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2006839.1774881078.1@sss.pgh.pa.us>
Date: Mon, 30 Mar 2026 10:31:18 -0400
Message-ID: <2006840.1774881078@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2006840.1774881078%40sss.pgh.pa.us>
Precedence: bulk

Ibrahim Shaame <ishaame@gmail.com> writes:
> Thanks for the reply. Both are integers and they work well without the two
> lines. So what changed one of them to text. Can you see where? I have not
> been able to identify.

This bit is forcing the column names for just the first three
output columns, leaving the rest to default from the SELECT
targetlist:

	WITH RECURSIVE x(jina, namba, nasaba_1) AS (

That's a hazardous practice: usually I'd force all or none of
the column names that way.  In this case, I speculate that you
carelessly added the new column as one of the physically first
three SELECT outputs, and didn't adjust this list to match,
leading to confusion about which column is "x.namba".

If that's not it, you need to be a great deal more specific
about exactly how you changed the query.

			regards, tom lane