Re: pg_dump incorrect output in plaintext mode

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump incorrect output in plaintext mode
Date: 2012-09-04 13:51:44
Message-ID: 15951.1346766704@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Aug 28, 2012 9:59 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Well, why don't we just s/restoring/processing/ in the debug message,
>>> and call it good?

> Are we "allowed" to backpatch things to 9.2 at this point that changes
> strings for translators?

Well, not being a translator I'm not sure that I get a vote.
But I'd think this is too minor to justify back-patching it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2012-09-04 13:52:28 Re: pg_dump incorrect output in plaintext mode
Previous Message Bruce Momjian 2012-09-04 13:47:49 Re: 9.2 pg_upgrade regression tests on WIndows