From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: meson oddities |
Date: | 2023-01-27 10:58:51 |
Message-ID: | 27e7ae15-3fa1-47af-2548-29a095a4dc2a@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 26.01.23 19:05, Andres Freund wrote:
>> Oh, that is interesting. In that case, this is not the right patch. We
>> should proceed with my previous patch in [0] then.
> WFM.
>
> I still think it'd be slightly more legible if we tested the prefix for
> postgres|pgsql once, rather than do the per-variable .contains() checks on the
> "combined" path.
Ok, committed with that change.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-01-27 11:00:07 | Re: Time delayed LR (WAS Re: logical replication restrictions) |
Previous Message | vignesh C | 2023-01-27 10:15:04 | Re: Deadlock between logrep apply worker and tablesync worker |