Thank you both for the explanations and the link to the discussion of
Pavel's patches.
Hi, according to the docs, RESET sets the value of a setting to
"The default value is defined as the value that the parameter would have
had, if no SET had ever been issued for it in the current session"
Which confuses me given that the value starts being NULL in the session and
then turns into an
problem, from
retrying like Tomas suggested to materialized CTEs that filter out
temporary relations before functions like pg_get_indexdef are called.
I will give these things a shot.
Regards.
On Sun, Aug 25, 2024 at 1:13 PM Adrian Klaver
wrote:
> On 8/25/24 08:36, Marcelo Zabani wrote:
&
Regards.
On Sun, Aug 25, 2024 at 12:06 PM Tomas Vondra wrote:
> On 8/25/24 15:42, Marcelo Zabani wrote:
> > Hi all,
> >
> > I can reproduce the error in the subject from time to time when querying
> > catalog tables while DDL is happening concurrently. Here's a
t be possible depending on query plan, I believe. But
again, an untested hypothesis.
On Sun, Aug 25, 2024 at 11:31 AM Ron Johnson
wrote:
> On Sun, Aug 25, 2024 at 9:42 AM Marcelo Zabani wrote:
>
>> Hi all,
>>
>> I can reproduce the error in the subject from time to time w
Hi all,
I can reproduce the error in the subject from time to time when querying
catalog tables while DDL is happening concurrently. Here's a bash script
that reproduces it (not always, you might have to run it many times until
you see ERROR: could not open relation with OID ):
#!/usr/bin/en
