From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Gavin M(dot) Roy" <gmr(at)myyearbook(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: SQL Function Slowness, 8.3.0 |
Date: | 2008-04-17 16:50:55 |
Message-ID: | 1208451055.4259.358.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, 2008-04-17 at 12:41 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > On Thu, 2008-04-17 at 12:12 -0400, Tom Lane wrote:
> >> Aren't these suggestions mutually contradictory?
>
> > No, they're orthogonal. The pretty printer would get the indenting and
> > line feeds correct, the obfuscator would replace actual names with "A",
> > "B" or "Table1" etc..
>
> Hmm, that's not what I'd call an "obfuscator", more an "anonymizer".
> Code obfuscators are generally intended to make code unreadable
> (in fact de-pretty-printing is one of their chief techniques).
That's a better term. I did say "name obfuscator" but I can see how that
was confusing, especially with the recent discussion on code
obfuscation. Sorry about that.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2008-04-17 17:00:43 | Re: SQL Function Slowness, 8.3.0 |
Previous Message | Tom Lane | 2008-04-17 16:41:12 | Re: SQL Function Slowness, 8.3.0 |