Hi,
On 2019-06-10 22:42:52 -0400, Alvaro Herrera wrote:
> On 2019-May-30, Andres Freund wrote:
> > On 2019-05-30 16:31:39 +0530, Ashutosh Sharma wrote:
> > > Here are some more details on the crash reported in my previous e-mail for
> > > better clarity:
> >
> > I'll look into this once pgcon is
Hi,
On 2019-05-30 16:31:39 +0530, Ashutosh Sharma wrote:
> > *Analysis:*
> > I did some quick investigation on this and found that when the aggregate
> > is performed on the first group i.e. group by 'a', all the input tuples are
> > fetched from the outer plan and stored into the tuplesort object
On 2019-May-30, Andres Freund wrote:
> Hi,
>
>
> On 2019-05-30 16:31:39 +0530, Ashutosh Sharma wrote:
> > Here are some more details on the crash reported in my previous e-mail for
> > better clarity:
>
> I'll look into this once pgcon is over... Thanks for finding!
Ping?
--
Álvaro Herrera
Hi,
On 2019-05-30 16:31:39 +0530, Ashutosh Sharma wrote:
> Here are some more details on the crash reported in my previous e-mail for
> better clarity:
I'll look into this once pgcon is over... Thanks for finding!
Greetings,
Andres Freund
Hi All,
Here are some more details on the crash reported in my previous e-mail for
better clarity:
The crash only happens when a *primary key* or *btree index* is created on
the test table. For example consider the following two scenarios.
*TC1: With PK*
create table t1(a int *primary key*, b te
Hi All,
I'm getting a server crash when executing the following test-case:
create table t1(a int primary key, b text);
insert into t1 values (1, 'aa'), (2, 'bb'), (3, 'aa'), (4, 'bb');
select a, b, array_agg(a order by a) from t1 group by grouping sets ((a),
(b));
*Backtrace:*
#0 0x7f37d063
