Re: BUG #18647: INSERT statements execute functions twice.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Todd Brandys <brandystodd(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #18647: INSERT statements execute functions twice.
Date: 2024-10-09 12:40:38
Message-ID: CAKFQuwZ10FfSqKvydqijuHJTSAqCZnF2RHkGhCiEZ58S+qk5Bw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wednesday, October 9, 2024, Todd Brandys <brandystodd(at)gmail(dot)com> wrote:

> Here is the CREATE table for party. It was nothing more than a test table
> at this time:
>
> CREATE TABLE party (
> uuid uuid NOT NULL,
> date_updated timestamp(0) NOT NULL,
> user_updated pg_catalog.regrole NOT NULL,
> organization uuid NOT NULL,
>
> CONSTRAINT pk_party
> PRIMARY KEY ( uuid )
> );
>

As an aside, using regrole is not a good idea. The meaning of the integer
that gets saved will change if you perform an upgrade or otherwise have to
rebuild the global role catalog table. User-space should not be storing
OID values.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Sabino Mullane 2024-10-09 13:55:58 Re: BUG #18647: INSERT statements execute functions twice.
Previous Message PG Bug reporting form 2024-10-09 12:36:42 BUG #18650: rhel-8-aarch64 yum repository for Postgres 13 is missing repodata