Re: pg_get_triggerdef in pg_dump - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_get_triggerdef in pg_dump
Date
Msg-id 12411.1055858958@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_get_triggerdef in pg_dump  (Andreas Pflug <Andreas.Pflug@web.de>)
Responses Re: pg_get_triggerdef in pg_dump  (Andreas Pflug <Andreas.Pflug@web.de>)
List pgsql-hackers
Andreas Pflug <Andreas.Pflug@web.de> writes:
> Difference from Christopher's solution is that mine utilizes completely 
> separatated (copied) code, so ruleutils code is still unchanged. This 
> was a concession to Tom who claimed concerns about pg_dump not being 
> able to reproduce things correctly if there was *any* error in it.

I recall objecting to someone who wanted to remove "unnecessary"
parentheses, but I can't see any risk in inserting unnecessary
whitespace.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: confused with encodings
Next
From: Tom Lane
Date:
Subject: Re: O_DIRECT in freebsd