Re: New Object Access Type hooks

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Joshua Brindle <joshua(dot)brindle(at)crunchydata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Joe Conway <joe(at)crunchydata(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: New Object Access Type hooks
Date: 2022-03-24 21:58:22
Message-ID: 20220324215822.xrr73lgt7vu2ll3g@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-03-24 17:44:31 -0400, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > On 3/24/22 16:59, Andres Freund wrote:
> >> I just rebased the meson tree (atop 75b1521dae1) and the test_oat_hooks test
> >> fail on windows with meson.
>
> > Even if you use NO_LOCALE=1/ENCODING=UTF8 as the Makefile now does?

I didn't do that, no. I guess I should have re-checked that in the makefile /
reread the commit message in more detail - although it really doesn't provide
a lot of that. That's, uh, some shoveling problems under the carpet.

I'll do that for now then.

> Note that that's basically a workaround for buggy placement of the
> OAT hooks, as per previous discussion. I hope that we fix that bug
> pretty soon, so it shouldn't really be a factor for the meson conversion.

Yea. I found it's a lot easier to rebase the meson tree frequently rather than
do it in larger batches, so I just do so every few days...

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2022-03-24 21:59:11 Re: logical decoding and replication of sequences
Previous Message David Rowley 2022-03-24 21:57:29 Re: automatically generating node support functions