Re: Dump public schema ownership & seclabels

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>, Asif Rehman <asifr.rehman@gmail.com>, Zhihong Yu <zyu@yugabyte.com>
Date: 2021-06-29T16:32:08Z
Lists: pgsql-hackers
Noah Misch <noah@leadboat.com> writes:
> On Tue, Jun 29, 2021 at 01:53:42AM -0400, Tom Lane wrote:
>> Noah Misch <noah@leadboat.com> writes:
>>> Done.  This upset one buildfarm member so far:
>>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gaur&dt=2021-06-29%2001%3A43%3A14

>> I'm too tired to look at it right now, but remembering that that's
>> running an old Perl version, I wonder if there's some Perl
>> incompatibility here.

> That's at least part of the problem, based on experiments on a machine with
> Perl 5.8.4.  That machine can't actually build PostgreSQL.  I've pushed a
> necessary fix, though I'm only about 80% confident about it being sufficient.

gaur is still plugging away on a new run, but it got past the
pg_dump-check step, so I think you're good.

prairiedog has a similar-vintage Perl, so likely it would have shown the
problem too; but it's slow enough that it never saw the intermediate state
between these commits.

			regards, tom lane



Commits

  1. Remove literal backslash from Perl \Q ... \E.

  2. Dump COMMENT ON SCHEMA public.

  3. Dump public schema ownership and security labels.