[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-performance
Subject:    Re: [PERFORM] Avoiding Recheck Cond when using Select Distinct
From:       Jeff Janes <jeff.janes () gmail ! com>
Date:       2013-02-25 18:48:51
Message-ID: CAMkU=1wo8qSLNut5ktkc4tpisOBVepTk=2BaFd4LmnkBLXh7jA () mail ! gmail ! com
[Download RAW message or body]

On Mon, Feb 25, 2013 at 10:11 AM, Maciek Sakrejda <m.sakrejda@gmail.com>wrote:

> On Sat, Feb 23, 2013 at 3:53 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> > It would really help to have "explain (analyze, buffers)".  Especially if
> > you turn on track_io_timing, (although that part probably can't be done
> on
> > Heroku, as it requires superuser access.)
>
> Right, that's not supported right now, although given that the
> superuser is primarily for performance considerations (right?),
> perhaps we should find some way of exposing this.
>


I don't think it is SUSET for performance reasons, as the ordinary user
already has plenty of ways to shoot themselves (and fellow users) in the
foot performance-wise.  I think it was based on the idea that those
tracking tools that the administrator has turned on, ordinary users may
turn off.  I think the other way around would be fine (if it is off for the
server, the user can still turn it on for their session--and presumably
also turn it off again if it is one only because they set it that way, not
because the administrator set it that way), but I think that that behavior
is not trivial to implement.  I looked in the archives, but the SUSET
nature of this doesn't seem to have been discussed.

Cheers,

Jeff

[Attachment #3 (text/html)]

<div class="gmail_quote">On Mon, Feb 25, 2013 at 10:11 AM, Maciek Sakrejda <span \
dir="ltr">&lt;<a href="mailto:m.sakrejda@gmail.com" \
target="_blank">m.sakrejda@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <div class="im">On Sat, Feb 23, 2013 at 3:53 PM, Jeff Janes \
&lt;<a href="mailto:jeff.janes@gmail.com">jeff.janes@gmail.com</a>&gt; wrote:<br> \
&gt; It would really help to have &quot;explain (analyze, buffers)&quot;.  Especially \
if<br> &gt; you turn on track_io_timing, (although that part probably can&#39;t be \
done on<br> &gt; Heroku, as it requires superuser access.)<br>
<br>
</div>Right, that&#39;s not supported right now, although given that the<br>
superuser is primarily for performance considerations (right?),<br>
perhaps we should find some way of exposing this.<br></blockquote><div><br><br>I \
don&#39;t think it is SUSET for performance reasons, as the ordinary user already has \
plenty of ways to shoot themselves (and fellow users) in the foot performance-wise.  \
I think it was based on the idea that those tracking tools that the administrator has \
turned on, ordinary users may turn off.  I think the other way around would be fine \
(if it is off for the server, the user can still turn it on for their session--and \
presumably also turn it off again if it is one only because they set it that way, not \
because the administrator set it that way), but I think that that behavior is not \
trivial to implement.  I looked in the archives, but the SUSET nature of this \
doesn&#39;t seem to have been discussed.<br>  <br>Cheers,<br><br>Jeff<br></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]