Horton

Re: Conflict between regression tests namespace & transactions due to recent changes

Marina Polyakova <m.polyakova@postgrespro.ru>

View thread View on postgr.es
From: Marina Polyakova <m.polyakova@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>, pgsql-hackers@postgresql.org, Noah Misch <noah@leadboat.com>, exclusion@gmail.com
Date: 2023-05-19T16:34:13Z
Lists: pgsql-hackers 
On 2023-05-19 17:59, Tom Lane wrote:
> Marina Polyakova <m.polyakova@postgrespro.ru> writes:
>> On 2023-05-19 09:03, Michael Paquier wrote:
>>> FYI, the buildfarm is seeing some spurious failures as well:
>>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=schnauzer&dt=2023-05-1904%3A29%3A42
> 
>> Yes, it is the same error. Here's another one in version 13:
>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=schnauzer&dt=2023-05-18%2022:37:49
> 
> Right.  I went ahead and pushed the fix in hopes of stabilizing things.
> (I went with "trans_abc" as the new table name, for consistency with
> some other nearby names.)
> 
> 			regards, tom lane

Thank you! I missed the same changes in version 11 :(

-- 
Marina Polyakova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Commits

  1. Avoid naming conflict between transactions.sql and namespace.sql.

  2. Replace last PushOverrideSearchPath() call with set_config_option().