Re: pg_dump --pretty-print-views - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump --pretty-print-views
Date
Msg-id 18172.1398784481@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump --pretty-print-views  (Keith Fiske <keith@omniti.com>)
Responses Re: pg_dump --pretty-print-views
Re: pg_dump --pretty-print-views
List pgsql-hackers
Keith Fiske <keith@omniti.com> writes:
> On Sun, Feb 3, 2013 at 4:06 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Applied with corrections.

> Was this ever committed into core? Apologies, I'm not very familiar with
> looking through the commit history of the source code and I don't see
> anything about this option or pretty-print outputs in the pg_dump/restore
> docs for 9.3. Had someone asking me about this feature for pg_extractor

Yeah, if I say "applied" that means I committed it.  Here's the commit
log entry:

Author: Tom Lane <tgl@sss.pgh.pa.us>
Branch: master Release: REL9_3_BR [62e666400] 2013-02-03 15:56:45 -0500
   Perform line wrapping and indenting by default in ruleutils.c.      This patch changes pg_get_viewdef() and allied
functionsso that   PRETTY_INDENT processing is always enabled.  Per discussion, only the   PRETTY_PAREN processing
(thatis, stripping of "unnecessary" parentheses)   poses any real forward-compatibility risk, so we may as well make
dump  output look as nice as we safely can.      Also, set the default wrap length to zero (i.e, wrap after each SELECT
 or FROM list item), since there's no very principled argument for the   former default of 80-column wrapping, and most
peopleseem to agree this   way looks better.      Marko Tiikkaja, reviewed by Jeevan Chalke, further hacking by Tom
Lane

As per the branch annotation, this is in 9.3 and up.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: includedir_internal headers are not self-contained
Next
From: Andres Freund
Date:
Subject: What about a castNode() macro?