Re: altering a column's collation leaves an invalid foreign key

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Paul Jungwirth <pj(at)illuminatedcomputing(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: altering a column's collation leaves an invalid foreign key
Date: 2024-11-30 07:44:54
Message-ID: f6428b46-bace-430e-a199-6ed4d62098a1@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 29.11.24 15:25, Marcos Pegoraro wrote:
> Em ter., 19 de nov. de 2024 às 13:27, Peter Eisentraut
> <peter(at)eisentraut(dot)org <mailto:peter(at)eisentraut(dot)org>> escreveu:
>
> 3. Some documentation updates to explain some of the differences
> between
> NO ACTION and RESTRICT better.
>
>
> There is a typo on your commit "doc: Improve description of referential
> actions"
>
> There is also a noticeable difference between <literal>ON UPDATE NO
> +    ACTION</literal> (the default) and <literal>NO UPDATE RESTRICT</
> literal>.
>
> Should be ON UPDATE RESTRICT, right ?

Fixed, thanks!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2024-11-30 08:28:31 Re: Memory leak in WAL sender with pgoutput (v10~)
Previous Message Kirill Reshke 2024-11-30 06:58:38 Re: Truncate logs by max_log_size