pgsql: Put back alternative-output expected files

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Put back alternative-output expected files
Date: 2025-12-03 15:37:29
Message-ID: E1vQov3-002bvF-0J@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Put back alternative-output expected files

These were removed in 5dee7a603f66, but that was too optimistic, per
buildfarm member prion as reported by Tom Lane. Mea (Álvaro's) culpa.

Author: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
Discussion: https://postgr.es/m/570630.1764737028@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/be25c77677285d3b1365bd19280b27771a1efbce

Modified Files
--------------
.../index-concurrently-upsert-predicate_1.out | 124 +++++++++++++++++++++
.../expected/index-concurrently-upsert_1.out | 124 +++++++++++++++++++++
2 files changed, 248 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2025-12-03 16:56:09 pgsql: Use "foo(void)" for definitions of functions with no parameters.
Previous Message Daniel Gustafsson 2025-12-03 14:24:47 pgsql: doc: Consistently use restartpoint in the documentation