Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nRcrV-0004xR-C9 for pgsql-docs@arkaria.postgresql.org; Tue, 08 Mar 2022 16:39:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nRcrT-0008Il-Le for pgsql-docs@arkaria.postgresql.org; Tue, 08 Mar 2022 16:38:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nRcrT-0008Ic-CT for pgsql-docs@lists.postgresql.org; Tue, 08 Mar 2022 16:38:59 +0000 Received: from mail-oi1-x234.google.com ([2607:f8b0:4864:20::234]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nRcrQ-0001aT-UI for pgsql-docs@lists.postgresql.org; Tue, 08 Mar 2022 16:38:58 +0000 Received: by mail-oi1-x234.google.com with SMTP id o64so5951215oib.7 for ; Tue, 08 Mar 2022 08:38:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=qMsSMD9JLuzdXSYR4ZjmzlG2m9kQB29QWv+UsbDIti4=; b=FaQ7S18w3b0zyw69R2mY/uBSxe9orz2g5QDx4SZzMsbG012WMls4XmQtJ1ROG49LX9 8ePuCgXIEEFYswG8yWXl7da5spo1KEqz+vPPI8/b6LdpcBz+RJ946iJkRsAR2OvDFK7I j4ANGCzWCZ7NoqKyPj07tA7qYDrBDObDKDxVYbEJE0IfZfu1NOmhDBr1UgC7xVtl99kZ uc0wc/40J6fbJ2E7W7e4o4PGVJN56ry2+Vp/oltdOI0Az3HTlIlhH4w3nFKJZ8Nmsd/i HEiEy4EYDFN6lEbuN7BSnFzR9VjQ/MHu4V/38OlQlVLnAXSQPALGgV+RCXSSNTygdASa k59A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=qMsSMD9JLuzdXSYR4ZjmzlG2m9kQB29QWv+UsbDIti4=; b=BSvVbBmQs8Omd82muv8qNaxdNWlJjOEJYKBlKemuMIlnvJY9U6S1BTR5fpQ0YR8Tto DSo2fPU4cyl3AOUhSzwNLHeV24kGO5Csk9K1CL0LMMhZMdbJhJrsdu1pVO/l/shSXwX1 22910q6TuzLkKVnHZ9VTBugUok92uwGMwyrixUhHeyygYnI28qGc2We//gLFo5ImWRyI luQP+dxErr7mYf3fiGWCHdJuuC0oP+x1/xetiXFvYiZkZi1vZe/ZFadfYLb9MEpaeLCA 4NJMgqDRiLw48VvzmvqTp96Qki81AxuzDXzFpqh+BCiLdwRY4iMT0xMjc8B/sLq6lLfc 2zfw== X-Gm-Message-State: AOAM533r1QZ3iEKfuBTAEGzuMNpvMa7EdXDGufNYuOSrMe9T6bMrqGt2 Td6FsDBrh3LTxfGA/dXJ1M9p/HsfrvUzuAKu2IMAu+mEhyw= X-Google-Smtp-Source: ABdhPJx6YCsw04n+mMx2kBAh5wd+7vLS/liox2Gk/hbivYAo9H46iWFY3yFM/EMe9E5zTb2FdG6hKmdIIYhbMsj3OYc= X-Received: by 2002:a05:6808:1204:b0:2d9:a01a:48d0 with SMTP id a4-20020a056808120400b002d9a01a48d0mr3262332oil.283.1646757536218; Tue, 08 Mar 2022 08:38:56 -0800 (PST) MIME-Version: 1.0 References: <164675354342.1369298.14513879086676370656@wrigleys.postgresql.org> In-Reply-To: <164675354342.1369298.14513879086676370656@wrigleys.postgresql.org> From: "David G. Johnston" Date: Tue, 8 Mar 2022 09:38:39 -0700 Message-ID: Subject: Re: Missing information about CREATE TRIGGER on temporary tables To: Sebastien Flaesch , Pg Docs Content-Type: multipart/alternative; boundary="000000000000fa3ff105d9b79d2d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000fa3ff105d9b79d2d Content-Type: text/plain; charset="UTF-8" On Tue, Mar 8, 2022 at 9:25 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-createtrigger.html > Description: > > To be confirmed by the developer community... > The reference page about CREATE TRIGGER should indicate if it's allowed to > create triggers on temp tables. > This seems to be the supported, but I was wondering what happens with the > trigger name when created on a temp table. > It appears that no conflict can occur with other processes, and the same > trigger name can be used by different processes. > Checking the system tables, it appears that the trigger is created in > user's > pg_my_temp_schema() ... > Assuming this was moderated and so delayed. Answered on the -sql list email thread: https://www.postgresql.org/message-id/CAKFQuwZNZzgpo%2BP8bF6HG%3DVMq9ZZaw2kpvpgq1KaaL59NFVUTw%40mail.gmail.com In short, temporary tables are tables, and the naming behavior is documented on this page. David J. --000000000000fa3ff105d9b79d2d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Mar 8, 2022 at 9:25 AM PG Doc comments form <noreply@postgresq= l.org> wrote:
The following documentation co= mment has been logged on the website:

Page: https://www.postgresql.org/docs/14/sq= l-createtrigger.html
Description:

To be confirmed by the developer community...
The reference page about CREATE TRIGGER should indicate if it's allowed= to
create triggers on temp tables.
This seems to be the supported, but I was wondering what happens with the trigger name when created on a temp table.
It appears that no conflict can occur with other processes, and the same trigger name can be used by different processes.
Checking the system tables, it appears that the trigger is created in user&= #39;s
pg_my_temp_schema() ...

Assuming this was= moderated and so delayed.=C2=A0 Answered on the -sql list email thread:

https://= www.postgresql.org/message-id/CAKFQuwZNZzgpo%2BP8bF6HG%3DVMq9ZZaw2kpvpgq1Ka= aL59NFVUTw%40mail.gmail.com

In short, temporar= y tables are tables, and the=C2=A0naming behavior is documented on this pag= e.

David J.

--000000000000fa3ff105d9b79d2d--