Re: pg_upgrade's exec_prog() coding improvement

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade's exec_prog() coding improvement
Date: 2012-08-27 18:31:59
Message-ID: 1346092289-sup-5896@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Alvaro Herrera's message of vie ago 24 11:44:33 -0400 2012:
> Actually it seems better to just get rid of the extra varargs function
> and just have a single exec_prog. The extra NULL argument is not
> troublesome enough, it seems. Updated version attached.

Applied (with some very minor changes).

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2012-08-27 19:13:45 Re: MySQL search query is not executing in Postgres DB
Previous Message Bruce Momjian 2012-08-27 18:09:21 Re: Optimize referential integrity checks (todo item)