Help with PhD Dissertation

2025-04-14 Thread Osmel Brito-Bigott
Hello everyone! 👋 I am conducting research for my PhD dissertation on the political economy of Open Source Software (OSS), focusing on how free-riding, responsibility, and incentives impact the sustainability of OSS projects. If you are a developer, contributor, maintainer, or user of OSS, your in

Re: ICU Collations and Collation Updates

2025-04-14 Thread Laurenz Albe
On Mon, 2025-04-14 at 19:24 +0200, Paul Foerster wrote: > Hi Tom, hi Laurenz > > On 14 Apr 2025, at 16:36, Tom Lane wrote: > > > > Laurenz Albe writes: > > > You would have to build PostgreSQL yourself with a fixed version of ICU > > > that you never upgrade if you want to avoid the problem. > [

Re: ICU Collations and Collation Updates

2025-04-14 Thread Paul Foerster
Hi Tom, hi Laurenz > On 14 Apr 2025, at 16:36, Tom Lane wrote: > > Laurenz Albe writes: >> You would have to build PostgreSQL yourself with a fixed version of ICU >> that you never upgrade if you want to avoid the problem. [...] > 2. It's at least *possible* to use your own fixed-version ICU >

Re: ICU Collations and Collation Updates

2025-04-14 Thread Jehan-Guillaume de Rorthais
Le Mon, 14 Apr 2025 10:36:40 -0400, Tom Lane a écrit : […] > 2. It's at least *possible* to use your own fixed-version ICU > library if you're desperate enough. I don't think that would work > too well for libc; you're stuck with what the platform provides. You're not so stuck with what the plat

Re: TRUNCATE ONLY with foreign keys and triggers disabled

2025-04-14 Thread Dimitrios Apostolou
On Mon, 14 Apr 2025, Adrian Klaver wrote: On 4/14/25 08:20, Dimitrios Apostolou wrote: On Mon, 14 Apr 2025, Adrian Klaver wrote: On 4/14/25 08:07, Laurenz Albe wrote:  On Mon, 2025-04-14 at 17:05 +0200, Dimitrios Apostolou wrote:  I meant the *referencing* table has just been  populate

Re: TRUNCATE ONLY with foreign keys and triggers disabled

2025-04-14 Thread Adrian Klaver
On 4/14/25 08:20, Dimitrios Apostolou wrote: On Mon, 14 Apr 2025, Adrian Klaver wrote: On 4/14/25 08:07, Laurenz Albe wrote:  On Mon, 2025-04-14 at 17:05 +0200, Dimitrios Apostolou wrote:  I meant the *referencing* table has just been  populated. I'm trying to delete the *referenced* table an

Re: TRUNCATE ONLY with foreign keys and triggers disabled

2025-04-14 Thread Adrian Klaver
On 4/14/25 08:07, Laurenz Albe wrote: On Mon, 2025-04-14 at 17:05 +0200, Dimitrios Apostolou wrote: I meant the *referencing* table has just been populated. I'm trying to delete the *referenced* table and I get the error. That would break the foreign key constraint, right? PostgreSQL cannot al

CREATE SCHEMA AUTHORIZATION and ALTER SCHEMA OWNER TO

2025-04-14 Thread Dominique Devienne
Hi. I'm on v16+. The DB owner ROLE has CREATEROLE, and obviously CREATE on the DB. So it can both CREATE SCHEMA, and CREATE ROLE. Yet it cannot CREATE SCHEMA AUTHORIZATION, and gets an ERROR: must be able to SET ROLE "..." Yet because this is v16+, thus the DB owner has ADMIN OPTION on the ROLEs

Re: TRUNCATE ONLY with foreign keys and triggers disabled

2025-04-14 Thread Dimitrios Apostolou
On Mon, 14 Apr 2025, Adrian Klaver wrote: On 4/14/25 08:07, Laurenz Albe wrote: On Mon, 2025-04-14 at 17:05 +0200, Dimitrios Apostolou wrote: I meant the *referencing* table has just been populated. I'm trying to delete the *referenced* table and I get the error. That would break the fo

Re: TRUNCATE ONLY with foreign keys and triggers disabled

2025-04-14 Thread Laurenz Albe
On Mon, 2025-04-14 at 17:05 +0200, Dimitrios Apostolou wrote: > I meant the *referencing* table has just been > populated. I'm trying to delete the *referenced* table and I get the > error. That would break the foreign key constraint, right? PostgreSQL cannot allow that. Yours, Laurenz Albe

Re: TRUNCATE ONLY with foreign keys and triggers disabled

2025-04-14 Thread Dimitrios Apostolou
On Mon, 14 Apr 2025, Dimitrios Apostolou wrote: On Mon, 14 Apr 2025, Tom Lane wrote: Dimitrios Apostolou writes: While doing TRUNCATE ONLY I get: ERROR: cannot truncate a table referenced in a foreign key constraint But in my case the table to be truncated is already empty, and the T

Re: TRUNCATE ONLY with foreign keys and triggers disabled

2025-04-14 Thread Dimitrios Apostolou
On Mon, 14 Apr 2025, Tom Lane wrote: Dimitrios Apostolou writes: While doing TRUNCATE ONLY I get: ERROR: cannot truncate a table referenced in a foreign key constraint But in my case the table to be truncated is already empty, and the TRIGGERS are disabled in all tables. IIRC, it will let

Re: TRUNCATE ONLY with foreign keys and triggers disabled

2025-04-14 Thread Tom Lane
Dimitrios Apostolou writes: > While doing TRUNCATE ONLY I get: >ERROR: cannot truncate a table referenced in a foreign key constraint > But in my case the table to be truncated is already empty, and the > TRIGGERS are disabled in all tables. IIRC, it will let you do it if you truncate both t

Re: ICU Collations and Collation Updates

2025-04-14 Thread Tom Lane
Laurenz Albe writes: > On Mon, 2025-04-14 at 08:28 +, Thomas Michael Engelke wrote: >> Is my understanding correct then in that this way the database >> collations never change, unless a manual intervention reinitialises the >> collations and reindexes the database (or appropriate indexes)? Ho

Re: Event-Triggers for DB owners instead of just SUPERUSER

2025-04-14 Thread Wolfgang Walther
Dominique Devienne: Can't event-triggers also be available to DB owners, instead of just SUPERUSER? There's a recent -hackers thread exactly about this: https://www.postgresql.org/message-id/flat/CAGRrpzbtYDkg7_xwfzrqByYgCJQbbL38tADyuN%2B6tAkbA-Pnkg%40mail.gmail.com Best, Wolfgang

Re: Event-Triggers for DB owners instead of just SUPERUSER

2025-04-14 Thread Dominique Devienne
On Mon, Apr 14, 2025 at 12:09 PM Wolfgang Walther wrote: > > From Dominique Devienne: > > Can't event-triggers also be available to DB owners, instead of just > > SUPERUSER? > > There's a recent -hackers thread exactly about this: > https://www.postgresql.org/message-id/flat/CAGRrpzbtYDkg7_xwfzrq

Re: ICU Collations and Collation Updates

2025-04-14 Thread Laurenz Albe
On Mon, 2025-04-14 at 08:28 +, Thomas Michael Engelke wrote: > Where I currently work my colleagues used libc collations before I > arrived. While using libc collations, they stumbled upon the collation > update problem after SLES updates (15.4 to 15.5) (collation version > difference for datab

TRUNCATE ONLY with foreign keys and triggers disabled

2025-04-14 Thread Dimitrios Apostolou
Hello list, While doing TRUNCATE ONLY I get: ERROR: cannot truncate a table referenced in a foreign key constraint But in my case the table to be truncated is already empty, and the TRIGGERS are disabled in all tables. I wonder, is there a deeper reason for this error, or is it just an im

Re: Interesting case of IMMUTABLE significantly hurting performance

2025-04-14 Thread Wolfgang Walther
Tom Lane: If you err in the other direction, you don't get slapped on the wrist that way. We're willing to inline VOLATILE functions, for instance, whether or not the contained expression is volatile. Similarly for STRICT, and I think parallel safety as well. So my own habit when writing a SQL f

Event-Triggers for DB owners instead of just SUPERUSER

2025-04-14 Thread Dominique Devienne
Hi. I'd like to use CREATE EVENT TRIGGER, but they are SUPERUSER only. In the past, CREATE EXTENSION was also SUPERUSER-only, but is now also available to DB owners. Which is great! Can't event-triggers also be available to DB owbers, instead of just SUPERUSER? Having CREATEDB does not imply ha

ICU Collations and Collation Updates

2025-04-14 Thread Thomas Michael Engelke
Good morning, long time reader, first time writer. Where I currently work my colleagues used libc collations before I arrived. While using libc collations, they stumbled upon the collation update problem after SLES updates (15.4 to 15.5) (collation version difference for database and operating sy