På tirsdag 27. februar 2018 kl. 12:16:42, skrev Jeevan Chalke <jeevan.chalke@enterprisedb.com>:Hi, On Tue, Feb 27, 2018 at 3:46 PM, Andreas Joseph Krogh <andreas@visena.com> wrote: $subject The query I'm using is 14K and I have not produced a test-case, so this is just a heads-up. Rajkumar off-list shared same issue with me. And I have posted a fix for the same (https://www.postgresql.org/message-id/CAM2+6=X9kxQoL2ZqZ00E6asBt9z+rfyWbOmhXJ0+8fPAyMZ9Jg@mail.gmail.com) Can you please check if that fixes your test-case or not? Applying fix_aggref_in_non-agg_error.patch (only) fixes the issue
Hi, On Tue, Feb 27, 2018 at 3:46 PM, Andreas Joseph Krogh <andreas@visena.com> wrote: $subject The query I'm using is 14K and I have not produced a test-case, so this is just a heads-up. Rajkumar off-list shared same issue with me. And I have posted a fix for the same (https://www.postgresql.org/message-id/CAM2+6=X9kxQoL2ZqZ00E6asBt9z+rfyWbOmhXJ0+8fPAyMZ9Jg@mail.gmail.com) Can you please check if that fixes your test-case or not?
$subject The query I'm using is 14K and I have not produced a test-case, so this is just a heads-up.
-- Andreas Joseph Krogh
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных
