Silence perl warning in check-world
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t36242psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 07:56 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t36242_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t36242_1 && git checkout t36242_1Patchset v1 (message #1) is on t36242_1
In some older versions of perl (like v5.10), I get a warning that:
Use of implicit split to @_ is deprecated at src/test/recovery/t/
006_logical_decoding.pl line 26.
Splitting into a dummy variable silences that warning, as in the attached.
There may be a better way to silence the warning. (Presumably it actually
is clobbering @_ in those older versions of Perl, but that doesn't seem to
cause problems in this particular case.)
Cheers,
Jeff
On 3/13/17 16:51, Jeff Janes wrote:
In some older versions of perl (like v5.10), I get a warning that:
Use of implicit split to @_ is deprecated at
src/test/recovery/t/006_logical_decoding.pl
<http://006_logical_decoding.pl> line 26.Splitting into a dummy variable silences that warning, as in the
attached. There may be a better way to silence the warning.
(Presumably it actually is clobbering @_ in those older versions of
Perl, but that doesn't seem to cause problems in this particular case.)
committed
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers