Re: Database-level collation version tracking

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Database-level collation version tracking
Date: 2022-02-14 09:14:35
Message-ID: 20220214091435.qozxiq6lmdtrw6bk@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Mon, Feb 14, 2022 at 09:55:19AM +0100, Peter Eisentraut wrote:
> I have committed this patch.

Great! Do you plan to send a rebased version of the ICU default collation
soon or should I start looking at the current v4?

> I didn't address the above issue. I looked at it a bit, but I also found
> other (non-database) object types that had a mix of different return types.
> It's not clear to me what this is all supposed to mean. If no one is
> checking the return, they should really all be turned into void, IMO. Maybe
> this should be a separate discussion.

Agreed.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-02-14 09:16:29 Re: Skipping logical replication transactions on subscriber side
Previous Message Kyotaro Horiguchi 2022-02-14 09:02:11 Re: Possible uninitialized use of the variables (src/backend/access/transam/twophase.c)