Re: pgsql: Harden new test case against force_parallel_mode = regress. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgsql: Harden new test case against force_parallel_mode = regress.
Date
Msg-id 2478846.1677861476@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Harden new test case against force_parallel_mode = regress.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pgsql: Harden new test case against force_parallel_mode = regress.  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pgsql: Harden new test case against force_parallel_mode = regress.  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Mar 2, 2023 at 5:47 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Per buildfarm: worker processes can't see a role created in
>> the current transaction.

> Now why would that happen? Surely the snapshot for each command is
> passed down from leader to worker, and the worker is not free to
> invent a snapshot from nothing.

The workers were failing at startup, eg (from [1]):

+ERROR:  role "regress_psql_user" does not exist
+CONTEXT:  while setting parameter "session_authorization" to "regress_psql_user"

Maybe this says that worker startup needs to install the snapshot before
doing any catalog accesses?  Anyway, I'd be happy to revert this test
hack if you care to make the case work.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: libpq: PQgetCopyData() and allocation overhead
Next
From: Matthias van de Meent
Date:
Subject: Re: pgsql: Harden new test case against force_parallel_mode = regress.