On Thu, Apr 21, 2022 at 12:18 PM Peter Geoghegan wrote:
> On Tue, Apr 12, 2022 at 11:01 AM Peter Geoghegan wrote:
> > Attached patch fixes the issue, and includes the test case that you posted.
>
> Pushed a similar patch just now. Backpatched to all supported branches.
Thanks.
On Tue, Apr 12, 2022 at 11:01 AM Peter Geoghegan wrote:
> Attached patch fixes the issue, and includes the test case that you posted.
Pushed a similar patch just now. Backpatched to all supported branches.
--
Peter Geoghegan
On Sun, Apr 3, 2022 at 4:34 PM Thomas Munro wrote:
> I probably should have made it clearer in the commit message,
> cc58eecc5 doesn't fix this problem in the master branch. It only
> fixes the code that incorrectly assumed that datum1 was always
> available.
Attached patch fixes the issue, and
On Mon, Apr 4, 2022 at 11:12 AM Peter Geoghegan wrote:
> We will need a backpatchable fix, since Thomas' recent fix (commit
> cc58eecc5d75a9329a6d49a25a6499aea7ee6fd6) only targeted the master
> branch.
I probably should have made it clearer in the commit message,
cc58eecc5 doesn't fix this
On Sun, Apr 3, 2022 at 1:22 AM John Naylor wrote:
> I can confirm the problem on v10 as well.
We will need a backpatchable fix, since Thomas' recent fix (commit
cc58eecc5d75a9329a6d49a25a6499aea7ee6fd6) only targeted the master
branch.
If we really needed the performance advantage of
On Sun, Apr 3, 2022 at 8:22 PM John Naylor wrote:
> On Sun, Apr 3, 2022 at 11:05 AM Thomas Munro wrote:
> > Independently of a problem with a recent commit, it seems that
> > $SUBJECT in all releases (well, I only tested as far back as 11).
>
> I can confirm the problem on v10 as well.
Thanks
On Sun, Apr 3, 2022 at 11:05 AM Thomas Munro wrote:
>
> Hi,
>
> Independently of a problem with a recent commit, it seems that
> $SUBJECT in all releases (well, I only tested as far back as 11).
I can confirm the problem on v10 as well.
--
John Naylor
EDB: http://www.enterprisedb.com
Hi,
Independently of a problem with a recent commit, it seems that
$SUBJECT in all releases (well, I only tested as far back as 11). I
attach an addition to the tests to show this, but here's a stand-alone
repro:
DROP TABLE IF EXISTS clstr_expression;
CREATE TABLE clstr_expression(id serial
