Re: Fix order of checking ICU options in initdb and create database

From: Марина Полякова <polyakova(dot)marina69(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org, andres(at)anarazel(dot)de
Subject: Re: Fix order of checking ICU options in initdb and create database
Date: 2022-11-19 11:42:08
Message-ID: CA+FhiewZpOL4kbSJAQy0s_yagxq-cJwtGOTpDCBHNA5mRFAKnw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

чт, 17 нояб. 2022 г. в 09:54, Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com>:
>
> On 29.10.22 15:09, Marina Polyakova wrote:
> > On 2022-10-29 14:33, Marina Polyakova wrote:
> >> Hello!
> >>
> >> This is the last proposed patch on this subject [1] moved to a
> >> separate thread for Commitfest..
> >
> > Also added a patch to export with_icu when running src/bin/scripts tests
> > [1].
>
> I have committed the meson change.

Thank you!

(Sorry, I'm having problems sending emails from corporate email :( )

--
Marina Polyakova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Марина Полякова 2022-11-19 12:12:29 Re: Fix order of checking ICU options in initdb and create database
Previous Message Peter Eisentraut 2022-11-19 11:00:12 Re: Polyphase merge is obsolete