Re: pg_dump incorrect output in plaintext mode

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

On Tue, Sep 4, 2012 at 3:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

Probably - that's why I didn't even consider going back beyond 9.2.

Anyway; I'll just leave it at master.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-09-04 14:35:07 Re: Some whitespaces in utility.c
Previous Message Tom Lane 2012-09-04 13:51:44 Re: pg_dump incorrect output in plaintext mode