Re: row literal problem - Mailing list pgsql-hackers

From Tom Lane
Subject Re: row literal problem
Date
Msg-id 29564.1342639805@sss.pgh.pa.us
Whole thread Raw
In response to Re: row literal problem  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: row literal problem  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 07/18/2012 03:18 PM, Merlin Moncure wrote:
>> there are no null fields, right? if the last field is sometimes null
>> you'd see that (you probably ruled that out though).  when you say
>> 'sometimes', do you mean for some rows and not others? or for some
>> queries?

> No, the inner query has two fields.

> It happens for all rows, but not for all two-field-resulting queries as 
> q. I'm trying to find a simple case rather than the rather complex query 
> my customer is using.

I'm wondering about a rowtype with a third, dropped column.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: row literal problem
Next
From: Tom Lane
Date:
Subject: bgwriter, regression tests, and default shared_buffers settings