On Tue, Aug 18, 2020 at 11:38:38AM +0200, Magnus Hagander wrote:
> On Tue, Aug 18, 2020 at 11:24 AM Dave Page wrote:
> Not necessarily. It's likely that not all indexes use ICU collations, and
> you still save time loading what may be large amounts of data.
>
> I agree though, that it
On Tue, Aug 18, 2020 at 11:39 AM Magnus Hagander wrote:
>
> On Tue, Aug 18, 2020 at 11:24 AM Dave Page wrote:
>>
>> On Mon, Aug 17, 2020 at 7:23 PM Bruce Momjian wrote:
>>>
>>> On Mon, Aug 17, 2020 at 04:55:13PM +0100, Dave Page wrote:
>> I wasn't aware that ICU had the concept of collation vers
Magnus Hagander schrieb am 18.08.2020 um 11:38:
> It might be a slightly larger percentage on Windows who use it, but
> I'm willing to bet it's still quite low.
I have seen increasingly more questions around ICU collations on Windows due to
the fact that people that migrate from SQL Server to Pos
On Tue, Aug 18, 2020 at 11:24 AM Dave Page wrote:
>
>
> On Mon, Aug 17, 2020 at 7:23 PM Bruce Momjian wrote:
>
>> On Mon, Aug 17, 2020 at 04:55:13PM +0100, Dave Page wrote:
>> > That was more if the installer actually handles the whole chain. It
>> clearly
>> > doesn't today (since it do
On Mon, Aug 17, 2020 at 7:23 PM Bruce Momjian wrote:
> On Mon, Aug 17, 2020 at 04:55:13PM +0100, Dave Page wrote:
> > That was more if the installer actually handles the whole chain. It
> clearly
> > doesn't today (since it doesn't support upgrades), I agree this might
> > definitely
On Tue, Aug 18, 2020 at 09:44:35AM +0900, Michael Paquier wrote:
> On Mon, Aug 17, 2020 at 02:23:57PM -0400, Bruce Momjian wrote:
> > Also, is it the ICU library version we should be tracking for reindex,
> > or each _collation_ version? If the later, do we store the collation
> > version for each
On Mon, Aug 17, 2020 at 02:23:57PM -0400, Bruce Momjian wrote:
> Also, is it the ICU library version we should be tracking for reindex,
> or each _collation_ version? If the later, do we store the collation
> version for each index?
You need to store the collation version(s) for each index. This
On Mon, Aug 17, 2020 at 04:55:13PM +0100, Dave Page wrote:
> That was more if the installer actually handles the whole chain. It
> clearly
> doesn't today (since it doesn't support upgrades), I agree this might
> definitely be overkill. But then also I don't really see the problem with
On Mon, Aug 17, 2020 at 4:14 PM Magnus Hagander wrote:
>
>
> On Mon, Aug 17, 2020 at 1:44 PM Dave Page wrote:
>
>>
>>
>> On Mon, Aug 17, 2020 at 11:19 AM Magnus Hagander
>> wrote:
>>
>>>
>>>
>>> On Fri, Aug 14, 2020 at 3:00 PM Bruce Momjian wrote:
>>>
On Tue, Aug 11, 2020 at 02:58:30PM +0
On Mon, Aug 17, 2020 at 1:44 PM Dave Page wrote:
>
>
> On Mon, Aug 17, 2020 at 11:19 AM Magnus Hagander
> wrote:
>
>>
>>
>> On Fri, Aug 14, 2020 at 3:00 PM Bruce Momjian wrote:
>>
>>> On Tue, Aug 11, 2020 at 02:58:30PM +0200, Magnus Hagander wrote:
>>> > On Tue, Aug 4, 2020 at 11:42 AM Dave Pag
On Mon, Aug 17, 2020 at 11:19 AM Magnus Hagander
wrote:
>
>
> On Fri, Aug 14, 2020 at 3:00 PM Bruce Momjian wrote:
>
>> On Tue, Aug 11, 2020 at 02:58:30PM +0200, Magnus Hagander wrote:
>> > On Tue, Aug 4, 2020 at 11:42 AM Dave Page wrote:
>> > That would require fairly large changes to the
On Fri, Aug 14, 2020 at 3:00 PM Bruce Momjian wrote:
> On Tue, Aug 11, 2020 at 02:58:30PM +0200, Magnus Hagander wrote:
> > On Tue, Aug 4, 2020 at 11:42 AM Dave Page wrote:
> > That would require fairly large changes to the installer to allow it
> to
> > login to the database server (whe
On Fri, Aug 14, 2020 at 10:23:27PM +0900, Michael Paquier wrote:
> We have nothing in core, yet, that helps with this kind of problem
> with binary upgrades. In the last year, Julien and I worked on an
> upgrade case where a glibc upgrade was involved with pg_upgrade used
> for PG, and it could no
On Fri, Aug 14, 2020 at 09:00:06AM -0400, Bruce Momjian wrote:
> On Tue, Aug 11, 2020 at 02:58:30PM +0200, Magnus Hagander wrote:
>> I assumed it had code for that stuff already. Mainly because I assumed it
>> supported doing pg_upgrade, which requires similar things no?
>
> While pg_upgrade requi
On Tue, Aug 11, 2020 at 02:58:30PM +0200, Magnus Hagander wrote:
> On Tue, Aug 4, 2020 at 11:42 AM Dave Page wrote:
> That would require fairly large changes to the installer to allow it to
> login to the database server (whether that would work would be dependent
> on
> how pg_hba.co
On Tue, 11 Aug 2020 at 13:45, Thomas Kellerer wrote:
>
> Jaime Casanova schrieb am 11.08.2020 um 20:39:
> >> As a follow-up to bug #16570 [1] and other previous discussions
> >> on the mailing-lists, I'm checking out PG13 beta for Windows
> >> from:
> >> https://www.enterprisedb.com/postgresql-e
Jaime Casanova schrieb am 11.08.2020 um 20:39:
As a follow-up to bug #16570 [1] and other previous discussions
on the mailing-lists, I'm checking out PG13 beta for Windows
from:
https://www.enterprisedb.com/postgresql-early-experience
and it ships with the same obsolete ICU 53 that was used
for
On Mon, 3 Aug 2020 at 13:56, Daniel Verite wrote:
>
> Hi,
>
> As a follow-up to bug #16570 [1] and other previous discussions
> on the mailing-lists, I'm checking out PG13 beta for Windows
> from:
> https://www.enterprisedb.com/postgresql-early-experience
> and it ships with the same obsolete IC
On Tue, Aug 4, 2020 at 11:42 AM Dave Page wrote:
>
>
> On Tue, Aug 4, 2020 at 10:29 AM Magnus Hagander
> wrote:
>
>> On Tue, Aug 4, 2020 at 10:07 AM Dave Page wrote:
>>
>>>
>>>
>>> On Tue, Aug 4, 2020 at 1:04 AM Bruce Momjian wrote:
>>>
On Mon, Aug 3, 2020 at 08:56:06PM +0200, Daniel Ver
On Tue, Aug 4, 2020 at 10:29 AM Magnus Hagander wrote:
> On Tue, Aug 4, 2020 at 10:07 AM Dave Page wrote:
>
>>
>>
>> On Tue, Aug 4, 2020 at 1:04 AM Bruce Momjian wrote:
>>
>>> On Mon, Aug 3, 2020 at 08:56:06PM +0200, Daniel Verite wrote:
>>> > Hi,
>>> >
>>> > As a follow-up to bug #16570 [1]
On Tue, Aug 4, 2020 at 10:07 AM Dave Page wrote:
>
>
> On Tue, Aug 4, 2020 at 1:04 AM Bruce Momjian wrote:
>
>> On Mon, Aug 3, 2020 at 08:56:06PM +0200, Daniel Verite wrote:
>> > Hi,
>> >
>> > As a follow-up to bug #16570 [1] and other previous discussions
>> > on the mailing-lists, I'm checki
Dave Page schrieb am 04.08.2020 um 10:06:
> Correct - updating ICU would mean a reindex is required following any
> upgrade, major or minor.
>
> I would really like to find an acceptable solution to this however as
> it really would be good to be able to update ICU.
>
What about providing a newer
On Tue, Aug 4, 2020 at 1:04 AM Bruce Momjian wrote:
> On Mon, Aug 3, 2020 at 08:56:06PM +0200, Daniel Verite wrote:
> > Hi,
> >
> > As a follow-up to bug #16570 [1] and other previous discussions
> > on the mailing-lists, I'm checking out PG13 beta for Windows
> > from:
> > https://www.enterpr
On Mon, Aug 3, 2020 at 08:56:06PM +0200, Daniel Verite wrote:
> Hi,
>
> As a follow-up to bug #16570 [1] and other previous discussions
> on the mailing-lists, I'm checking out PG13 beta for Windows
> from:
> https://www.enterprisedb.com/postgresql-early-experience
> and it ships with the same
Hi,
As a follow-up to bug #16570 [1] and other previous discussions
on the mailing-lists, I'm checking out PG13 beta for Windows
from:
https://www.enterprisedb.com/postgresql-early-experience
and it ships with the same obsolete ICU 53 that was used
for PG 10,11,12.
Besides not having the latest
25 matches
Mail list logo
