On Wed, Oct 11, 2017 at 2:11 PM Andres Freund wrote:
> I've pushed this. Thanks for the report & fix!
>
Excellent, thanks!
Best,
Lukas
--
Lukas Fittl
>> }
>> else if (QueryCancelPending)
>> {
>> /* handle interrupt */
>> }
>>
>
Which is implemented in the attached patch.
Unless someone wants to pick this up right away, I'll register it in the
next commitfest tomorrow.
fety margin.
>
Makes sense, guess I was overthinking this one.
Best,
Lukas
--
Lukas Fittl
Skype: lfittl
Phone: +1 415 321 0630 <(415)%20321-0630>
se demonstrating
> that, too.
>
I already had a separate patch that adds more regression tests (),
including one for prepared statements in the initial email.
Merged together now into one patch to keep it simple, and added another
constant value to the prepared
primary user-visible benefit in core.
I'd be happy to add a docs section showing how to use this, if there is
some consensus that its worth pursuing this direction.
Thanks for all the comments, appreciate the discussion.
Best,
Lukas
--
Lukas Fittl
fort needed.
[0] https://www.postgresql.org/message-id/CAM-w4HNOeNW6pY_1%
3DLp1aJGMmZ_R6S8JHjqvJMv8-%3DOf3q1q0w%40mail.gmail.com
Best,
Lukas
--
Lukas Fittl
PREPARE/EXECUTE with pg_stat_statements output.
B is intentionally simple, and would address the primary issue at hand
(distinguishing from the ? operator).
I'm also adding this patch to the commitfest starting tomorrow.
Best,
Lukas
[0] https://github.com/lfittl/pg_query#parsing-a-normaliz
n the
out-of-band query text file, and whether a patch for this would be
considered acceptable?
Best,
Lukas
--
Lukas Fittl
Skype: lfittl
Phone: +1 415 321 0630
attuple - those bloat estimation queries can be wildly
off at times.
See also https://www.postgresql.org/docs/9.5/static/pgstattuple.html as
well as https://www.keithf4.com/checking-for-postgresql-bloat/
Best,
Lukas
--
Lukas Fittl
Skype: lfittl
Phone: +1 415 321 0630
of the list helps
anyone really.
I see pg_stat_statements as a high-level overview of which queries have
run, and which ones you might want to look into closer using e.g.
auto_explain.
Best,
Lukas
--
Lukas Fittl
Skype: lfittl
Phone: +1 415 321 0630
sql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Lukas Fittl
Skype: lfittl
Phone: +1 415 321 0630
;ve done it).
You can solve this using a security definer method created by a superuser,
see
https://gist.github.com/lfittl/9ee78ac200e4e7ebe33d
for a full example.
--
Lukas Fittl
Skype: lfittl
Phone: +1 415 321 0630
, but with a JSON output format.
Note that an important detail in the monitoring case is that you don't
necessarily have the statement's underlying relations available (since you
might work with statistics data on a different machine).
Best,
Lukas
--
Lukas Fittl
Skype: lfittl
Phone: +1 415 321 0630
ser.
I believe the recent work on deparsing DDL statements relates to some of
that (i.e. might be re-usable for this purpose, through an extension), if
I'm understanding correctly.
[0]: https://github.com/pganalyze/pg_query
Best,
Lukas
--
Lukas Fittl
Skype: lfittl
Phone: +1 415 321 0630
from the outside, getting a list of tables from a query is trivial - but if
you need the oids you'll have to do it like pgpool does.
(feel free to ping me off-list about this)
Best,
--
Lukas Fittl
Skype: lfittl
Phone: +43 6991 2770651
15 matches
Mail list logo