On Monday, June 24, 2013 8:59 PM Борис Ромашов wrote:
> Amit, where should I post to force developing this feature ?
You can post this to pgsql-hackers, but I think it would be more better if you
can check if any other database support that feature.
I feel you need a more strong case for any deve
Thank you for the advice. Shortly after submitting this bug I found
Tom Lane's suggestion here
http://www.postgresql.org/message-id/201109082233.p88mxbge026...@wwwmaster.postgresql.org
Once we had the core dump we were quickly able to figure out that the
problem was in one our custom functions.
Amit, where should I post to force developing this feature ?
2013/6/24 Amit Kapila
> On Monday, June 24, 2013 1:23 PM Борис Ромашов wrote:
> >> Why do you want to know the exact row due to which this happens, and
> what you want to do with it?
> > Suppose I have a query that should select somet
On Monday, June 24, 2013 1:23 PM Борис Ромашов wrote:
>> Why do you want to know the exact row due to which this happens, and what
>> you want to do with it?
> Suppose I have a query that should select something and this query has some
> subquery that is (possibly by error) supposed to return onl
>> Why do you want to know the exact row due to which this happens, and
what you want to do with it?
Suppose I have a query that should select something and this query has some
subquery that is (possibly by error) supposed to return only one row, i.e.
I mean that it fetches smth unique. But for som
On Friday, June 21, 2013 1:24 PM Борис Ромашов wrote:
> I just realized that I wanted to ask about another error.
> more than one row returned by a subquery used as an expression
> not about
> subquery must return only one column
> 2013/6/21 Борис Ромашов
> Tom, suppose you haven't understood wha
