MIME-Version: 1.0
References: 
 <CAPpHfdsOkkeobCfO9hJvaE2fRcdGmWJoX0umx--DnApmtmefCg@mail.gmail.com>
 <CAJDiXgjNySH7Od3nZGjWy30sKv+-12c=kajL7Qfkj3y+CDRwtA@mail.gmail.com>
 <CAPpHfds8pwuwF69JFs0SQz58op-U4ddR3KWv0NVEij2mpkzgpw@mail.gmail.com>
 <239d181d-1415-49ee-ad57-b307f1a7ba66@uni-muenster.de>
 <CAJDiXgi_SW3DVvXb4+n04NA1YfeeXmT3gUnSG7h4JwBd+RdJGg@mail.gmail.com>
 <0e666e40-d003-4c92-95cf-1a33a647401f@uni-muenster.de>
 <CAJDiXgiyy+GG6a5=nDPQeOQTjdQo53+6N0rAzZ=M3baWGPJNsA@mail.gmail.com>
 <CAPpHfdsS49OTo2Af2GeoKJD-1Dy-hOzbje_AWOa_bw5Q9kEi7w@mail.gmail.com>
 <af2AdMw3HjXgkzWJ@paquier.xyz>
 <CAPpHfdsJM3KRLkkSqijmdJnw+y-ofwCyaAJCSpjxCbThT3oTew@mail.gmail.com>
 <agVyikiyMpPgaCU4@paquier.xyz>
 <CAPpHfdt10LO=8SYJthKZTqYeJV-RrdoUVCQVWPZj5zFs4wT3VA@mail.gmail.com>
In-Reply-To: 
 <CAPpHfdt10LO=8SYJthKZTqYeJV-RrdoUVCQVWPZj5zFs4wT3VA@mail.gmail.com>
From: Daniil Davydov <3danissimo@gmail.com>
Date: Thu, 14 May 2026 23:48:48 +0700
Message-ID: 
 <CAJDiXghqLUTrL2PmD2z=Zi360S_L3U8tTWvKm8GTZW9C5mAnbg@mail.gmail.com>
Subject: Re: Fix bug with accessing to temporary tables of other sessions
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
 Jim Jones <jim.jones@uni-muenster.de>,
	Soumya S Murali <soumyamurali.work@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	Stepan Neretin <slpmcf@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
	Mohamed Ali <moali.pg@gmail.com>, Nazneen Jafri <jafrinazneen@gmail.com>,
	Shawn McCoy <shawn.the.mccoy@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAJDiXghqLUTrL2PmD2z%3DZi360S_L3U8tTWvKm8GTZW9C5mAnbg%40mail.gmail.com>
Precedence: bulk

Hi,

On Thu, May 14, 2026 at 8:39=E2=80=AFPM Alexander Korotkov <aekorotkov@gmai=
l.com> wrote:
>
> On Thu, May 14, 2026 at 9:58=E2=80=AFAM Michael Paquier <michael@paquier.=
xyz> wrote:
> > On Thu, May 14, 2026 at 09:12:58AM +0300, Alexander Korotkov wrote:
> > > On Fri, May 8, 2026 at 9:19=E2=80=AFAM Michael Paquier <michael@paqui=
er.xyz> wrote:
> > >> If you wish me to look at this patch set in details, I may be able t=
o
> > >> do so around the beginning of next week.  I'm not sure that there is=
 a
> > >> strong urgency in tackling this issue for this minor release, this
> > >> could wait a bit more..
> > >
> > > Any news from your side?
> >
> > (Forgot -hackers and other folks in CC, sorry about that.)
> >
> > Unfortunately I have not been able to get back to it this week, and
> > next week is moot.  Perhaps it is better to not wait for me here, so
> > feel free to go ahead as you feel.
>
> Thank you for noticing.  I've pushed this today.  I have to slightly
> revise the tests to run on 18 and 17 (different log messages, and
> default value of log_lock_waits).
>

Thank you very much for your help!)

BTW, we still have another problem with temp tables. Tom wrote [1] about it
within this thread:

> Reality is that we cannot know whether an
> unqualified-name RangeVar references a temp table until we do a
> catalog lookup, so IMO we should not have a relpersistence field there
> at all. At best it means something quite different from what it means
> elsewhere, and that's a recipe for confusion. But changing that would
> not be a bug fix (AFAIK) but refactoring to reduce the probability of
> future bugs.

I'll try to implement that next month. But if someone gets ahead of me, ple=
ase
attach me in CC of the new thread.

[1] https://www.postgresql.org/message-id/4075754.1774378690%40sss.pgh.pa.u=
s

--
Best regards,
Daniil Davydov