Re: Proposal: Conflict log history table for Logical Replication

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Proposal: Conflict log history table for Logical Replication
Date: 2026-06-26 03:43:57
Message-ID: CAHut+Pv1Ls3Jq6AAmJzxjOJP-+=z6EeSpZ9-N4tzOfWFZp51UA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

A question for v58-0002.

======
src/test/regress/expected/subscription.out

+-- Trying to create a new table manually in the pg_conflict namespace
+-- This should fail as the namespace is reserved for conflict log tables
+CREATE TABLE pg_conflict.manual_table (id int);
+ERROR: permission denied for schema pg_conflict
+LINE 1: CREATE TABLE pg_conflict.manual_table (id int);
+ ^

Why is that error very different from the error received when
attempting the same thing for `pg_catalog` schema?
Shouldn't the errors in both cases be almost the same?

Here:
- LINE is shown
- A schema error happens instead of a create table error

OTOH, the similar case for pg_catalog looks like:
test_pub=# create table pg_catalog.t1(a int);
ERROR: permission denied to create "pg_catalog.t1"
DETAIL: System catalog modifications are currently disallowed.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirk Wolak 2026-06-26 03:51:53 Re: Global temporary tables
Previous Message wenhui qiu 2026-06-26 03:43:48 [PATCH] Adjust autovacuum thresholds using relallvisible