Re: pgsql: Add standard collation UNICODE

2023-03-10 Thread Jeff Davis
On Fri, 2023-03-10 at 11:52 -0800, Jonathan S. Katz wrote: > > The capitals should be first. That is not true in a lot of natural language locales, whether libc or ICU. The following return true for me (collencoding UTF-8): select 'abc' collate "en_US" < 'ABC' collate "en_US"; select 'abc'

Re: pgsql: Add standard collation UNICODE

2023-03-10 Thread Jonathan S. Katz
> On Mar 10, 2023, at 11:44 AM, Jeff Davis wrote: > > On Fri, 2023-03-10 at 12:42 +, Peter Eisentraut wrote: >>> Add standard collation UNICODE > > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion=2023-03-10%2018%3A58%3A04 > > Looks like there's still a failure, even after

Re: pgsql: Add standard collation UNICODE

2023-03-10 Thread Jeff Davis
On Fri, 2023-03-10 at 12:42 +, Peter Eisentraut wrote: > > Add standard collation UNICODE https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion=2023-03-10%2018%3A58%3A04 Looks like there's still a failure, even after subsequent fix 3e623ebc7a. I'm wondering how that diff happens,

pgsql: Ensure COPY TO on an RLS-enabled table copies no more than it sh

2023-03-10 Thread Tom Lane
Ensure COPY TO on an RLS-enabled table copies no more than it should. The COPY documentation is quite clear that "COPY relation TO" copies rows from only the named table, not any inheritance children it may have. However, if you enabled row-level security on the table then this stopped being

pgsql: Ensure COPY TO on an RLS-enabled table copies no more than it sh

2023-03-10 Thread Tom Lane
Ensure COPY TO on an RLS-enabled table copies no more than it should. The COPY documentation is quite clear that "COPY relation TO" copies rows from only the named table, not any inheritance children it may have. However, if you enabled row-level security on the table then this stopped being

pgsql: Ensure COPY TO on an RLS-enabled table copies no more than it sh

2023-03-10 Thread Tom Lane
Ensure COPY TO on an RLS-enabled table copies no more than it should. The COPY documentation is quite clear that "COPY relation TO" copies rows from only the named table, not any inheritance children it may have. However, if you enabled row-level security on the table then this stopped being

pgsql: Ensure COPY TO on an RLS-enabled table copies no more than it sh

2023-03-10 Thread Tom Lane
Ensure COPY TO on an RLS-enabled table copies no more than it should. The COPY documentation is quite clear that "COPY relation TO" copies rows from only the named table, not any inheritance children it may have. However, if you enabled row-level security on the table then this stopped being

pgsql: Ensure COPY TO on an RLS-enabled table copies no more than it sh

2023-03-10 Thread Tom Lane
Ensure COPY TO on an RLS-enabled table copies no more than it should. The COPY documentation is quite clear that "COPY relation TO" copies rows from only the named table, not any inheritance children it may have. However, if you enabled row-level security on the table then this stopped being

pgsql: Ensure COPY TO on an RLS-enabled table copies no more than it sh

2023-03-10 Thread Tom Lane
Ensure COPY TO on an RLS-enabled table copies no more than it should. The COPY documentation is quite clear that "COPY relation TO" copies rows from only the named table, not any inheritance children it may have. However, if you enabled row-level security on the table then this stopped being

pgsql: initdb: derive encoding from locale for ICU; similar to libc.

2023-03-10 Thread Jeff Davis
initdb: derive encoding from locale for ICU; similar to libc. Previously, the default encoding was derived from the locale when using libc; while the default was always UTF-8 when using ICU. That would throw an error when the locale was not compatible with UTF-8. This commit causes initdb to

pgsql: Fix tests for non-ICU build

2023-03-10 Thread Peter Eisentraut
Fix tests for non-ICU build missed in 0d21d4b9bc Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3e623ebc7a22444ad3d15b36ffa3273c47283e18 Modified Files -- src/test/regress/expected/collate.icu.utf8.out | 2 +-

pgsql: Add standard collation UNICODE

2023-03-10 Thread Peter Eisentraut
Add standard collation UNICODE This adds a new predefined collation named UNICODE, which sorts by the default Unicode collation algorithm specifications, per SQL standard. This only works if ICU support is built. Reviewed-by: Jeff Davis Discussion:

pgsql: Include headers of archive/ in installation

2023-03-10 Thread Michael Paquier
Include headers of archive/ in installation These new headers have been recently added in 35739b8, but they were not installed. Sravan has provided the patch for configure/make, while I have fixed the meson part. Author: Sravan Kumar, Michael Paquier Discussion:

pgsql: Add a test for UCS_BASIC collation

2023-03-10 Thread Peter Eisentraut
Add a test for UCS_BASIC collation Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/012ee842590d7bb56f250c15e00a8611ba0ae1da Modified Files -- src/test/regress/expected/collate.icu.utf8.out | 10 ++

pgsql: doc: Better example for custom ICU rules

2023-03-10 Thread Peter Eisentraut
doc: Better example for custom ICU rules Use a more practical example, and also add some explanation. Reported-by: Jeff Davis Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/cd427859745af4574d75e37ec7d427ccd2b8b24a Modified Files --