pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Schema obfuscator for performance question
3+ messages / 3 participants
[nested] [flat]

* Schema obfuscator for performance question
@ 2013-03-04 21:31  Joseph Pravato <joseph.pravato@nomagic.com>
  0 siblings, 2 replies; 3+ messages in thread

From: Joseph Pravato @ 2013-03-04 21:31 UTC (permalink / raw)
  To: pgsql-performance

Good Afternoon,

We are having a performance issue with our views in PostgreSQL and based
on the requirements for assistance you recommend providing the full
table and index schema besides additional information from this site.
https://wiki.postgresql.org/wiki/Slow_Query_Questions

We have been unsuccessful in finding a tool to obfuscate the schema
before providing it for review, is there an open source tool you
recommend to use?

Thanks!

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Schema obfuscator for performance question
@ 2013-03-04 21:37  Victor Yegorov <vyegorov@gmail.com>
  parent: Joseph Pravato <joseph.pravato@nomagic.com>
  1 sibling, 0 replies; 3+ messages in thread

From: Victor Yegorov @ 2013-03-04 21:37 UTC (permalink / raw)
  To: Joseph Pravato <joseph.pravato@nomagic.com>; +Cc: pgsql-performance

2013/3/4 Joseph Pravato <joseph.pravato@nomagic.com>

>  We are having a performance issue with our views in PostgreSQL and based
> on the requirements for assistance you recommend providing the full table
> and index schema besides additional information from this site.
> https://wiki.postgresql.org/wiki/Slow_Query_Questions
>
> **
>
> We have been unsuccessful in finding a tool to obfuscate the schema before
> providing it for review, is there an open source tool you recommend to use?
>

You can anonymize EXPLAIN output here: http://explain.depesz.com/

Not sure bout the schema...


-- 
Victor Y. Yegorov

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Schema obfuscator for performance question
@ 2013-03-04 21:37  Claudio Freire <klaussfreire@gmail.com>
  parent: Joseph Pravato <joseph.pravato@nomagic.com>
  1 sibling, 0 replies; 3+ messages in thread

From: Claudio Freire @ 2013-03-04 21:37 UTC (permalink / raw)
  To: Joseph Pravato <joseph.pravato@nomagic.com>; +Cc: pgsql-performance

On Mon, Mar 4, 2013 at 6:31 PM, Joseph Pravato
<joseph.pravato@nomagic.com> wrote:
> Good Afternoon,
>
> We are having a performance issue with our views in PostgreSQL and based on
> the requirements for assistance you recommend providing the full table and
> index schema besides additional information from this site.
> https://wiki.postgresql.org/wiki/Slow_Query_Questions
>
> We have been unsuccessful in finding a tool to obfuscate the schema before
> providing it for review, is there an open source tool you recommend to use?
>
> Thanks!

Without getting into the ugly business of asking why you'd want to
obfuscate schema, I can imagine a few (wrong) answers, I'll start by
noting that schema transmits meaning in the very names used, so
obfuscation, especially automatic and mindless obfuscation, will make
the problem a lot harder to review, because it will be a lot harder to
understand the schema.

So... I'd suggest, if you need obfuscation, that it should be done
manually, so that you may preserve meaningful names.


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2013-03-04 21:37 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-03-04 21:31 Schema obfuscator for performance question Joseph Pravato <joseph.pravato@nomagic.com>
2013-03-04 21:37 ` Victor Yegorov <vyegorov@gmail.com>
2013-03-04 21:37 ` Claudio Freire <klaussfreire@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox