Re: pgsql: Make new strings more alike previously existing messages. - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Make new strings more alike previously existing messages.
Date
Msg-id 24097.1239663420@sss.pgh.pa.us
Whole thread Raw
In response to pgsql: Make new strings more alike previously existing messages.  (alvherre@postgresql.org (Alvaro Herrera))
Responses Re: pgsql: Make new strings more alike previously existing messages.
List pgsql-committers
alvherre@postgresql.org (Alvaro Herrera) writes:
> Make new strings more alike previously existing messages.

This patch changed the meaning of one of the messages:

*************** main(int argc, char **argv)
*** 316,322 ****
      /* Can't do single-txn mode with multiple connections */
      if (opts->single_txn && opts->number_of_jobs > 1)
      {
!         fprintf(stderr, _("%s: cannot specify both --single-transaction and multiple jobs\n"),
                  progname);
          exit(1);
      }
--- 316,322 ----
      /* Can't do single-txn mode with multiple connections */
      if (opts->single_txn && opts->number_of_jobs > 1)
      {
!         fprintf(stderr, _("%s: options -1/--single-transaction and -j/--jobs cannot be used together\n"),
                  progname);
          exit(1);
      }

As the comment and the code itself show, "-j 1" works just fine with
--single-transaction.  The original wording reflected that, the new does
not.

Maybe this amount of imprecision is acceptable, but "make it look more
like the other messages" doesn't seem to me like enough justification.

            regards, tom lane

pgsql-committers by date:

Previous
From: alvherre@postgresql.org (Alvaro Herrera)
Date:
Subject: pgsql: Make new strings more alike previously existing messages.
Next
From: alvherre@postgresql.org (Alvaro Herrera)
Date:
Subject: pgsql: pg_restore -jN does not equate "multiple jobs", so partly revert