On 2019-11-02 16:00, Tom Lane wrote:
Peter Eisentraut writes:
This patch moves the parse analysis component of ExecuteQuery() and
EvaluateParams() into a new transformExecuteStmt() that is called from
transformStmt().
Uhmm ... no actual patch attached?
Oops, here it is.
--
Peter Eisentraut
>
>
> This is somewhat similar to a memory usage problem with a
> parallel query where each worker is allowed to use up to work_mem of
> memory. We can say that the users using parallel operation can expect
> more system resources to be used as they want to get the operation
> done faster, so we a
On Mon, 4 Nov 2019 at 14:02, Amit Kapila wrote:
>
> On Fri, Nov 1, 2019 at 2:21 PM Masahiko Sawada wrote:
> >
> > I think that two approaches make parallel vacuum worker wait in
> > different way: in approach(a) the vacuum delay works as if vacuum is
> > performed by single process, on the other
Hi Tels!
Thanks for your interest in fast decompression.
> 3 нояб. 2019 г., в 12:24, Tels написал(а):
>
> I wonder if you agree and what would happen if you try this variant on your
> corpus tests.
I've tried some different optimization for literals. For example loop
unrolling[0] and literals
For parallel vacuum [1], we were discussing what is the best way to
divide the cost among parallel workers but we didn't get many inputs
apart from people who are very actively involved in patch development.
I feel that we need some more inputs before we finalize anything, so
starting a new thread.
On Mon, Nov 4, 2019 at 10:32 AM Amit Kapila wrote:
>
> On Fri, Nov 1, 2019 at 2:21 PM Masahiko Sawada wrote:
> >
> > I think that two approaches make parallel vacuum worker wait in
> > different way: in approach(a) the vacuum delay works as if vacuum is
> > performed by single process, on the oth
On Mon, Nov 4, 2019 at 10:45 AM Amit Kapila wrote:
>
> On Sun, Nov 3, 2019 at 9:49 AM Dilip Kumar wrote:
> >
> > On Fri, Nov 1, 2019 at 2:21 PM Masahiko Sawada
> > wrote:
> > >
> > >
> > > I think that two approaches make parallel vacuum worker wait in
> > > different way: in approach(a) the va
On Sun, Nov 3, 2019 at 9:49 AM Dilip Kumar wrote:
>
> On Fri, Nov 1, 2019 at 2:21 PM Masahiko Sawada wrote:
> >
> >
> > I think that two approaches make parallel vacuum worker wait in
> > different way: in approach(a) the vacuum delay works as if vacuum is
> > performed by single process, on the
On Sat, Nov 2, 2019 at 8:01 PM Tom Lane wrote:
> amul sul writes:
> > I wondered can we have a shortcut somewhat similar to following POC
> > in recomputeNamespacePath () when the recomputed path is the same as the
> > previous baseSearchPath/activeSearchPath :
> > + /* TODO: POC */
> > + if
On Fri, Nov 1, 2019 at 2:21 PM Masahiko Sawada wrote:
>
> I think that two approaches make parallel vacuum worker wait in
> different way: in approach(a) the vacuum delay works as if vacuum is
> performed by single process, on the other hand in approach(b) the
> vacuum delay work for each workers
Greetings,
* Andrew Dunstan (andrew.duns...@2ndquadrant.com) wrote:
> On 11/1/19 12:58 PM, Robert Haas wrote:
> > On Thu, Oct 31, 2019 at 4:58 PM Andrew Dunstan
> > wrote:
> >> This patch allows the superuser to grant passwordless connection rights
> >> in postgres_fdw user mappings.
> > This is
On Fri, Nov 1, 2019 at 2:21 AM Julien Rouhaud wrote:
> Are you planning to continue working on it? For the record, that's
> something needed to be able to implement a filter in REINDEX command
> [1].
Bonjour Julien,
Unfortunately I haven't had time to work on it seriously, but here's a
quick re
Buildfarm member drongo has been failing the pg_ctl regression test
pretty often. I happened to look closer at what's happening, and
it's this:
could not read
"C:/prog/bf/root/HEAD/pgsql.build/src/bin/pg_ctl/tmp_check/t_004_logrotate_primary_data/pgdata/current_logfiles":
Permission denied at C
On Thu, Oct 31, 2019 at 3:03 AM Dave Cramer wrote:
> Ok, I've rebased and reverted logicalrep_read_insert
Hi Dave,
>From the code style police (actually just from cfbot, which is set up
to complain about declarations after statements, a bit of C99 we
aren't ready for):
proto.c:557:6: error: ISO
On Thu, Oct 17, 2019 at 3:22 PM Smith, Peter wrote:
> We have resurrected this 2 year old "SQL statements statistics counter"
> proposal from Hari.
>
> The attached patch addresses the previous review issues.
Hi,
No comment on the patch but I noticed that the documentation changes
don't build.
On Mon, Oct 28, 2019 at 1:52 PM Dilip Kumar wrote:
>
> On Mon, Oct 28, 2019 at 12:20 PM Amit Kapila wrote:
> >
> > On Sun, Oct 27, 2019 at 12:52 PM Dilip Kumar wrote:
> > >
> > > On Fri, Oct 25, 2019 at 9:19 PM Masahiko Sawada
> > > wrote:
> > > >
> > > >
> > > I haven't yet read the new set o
On Thu, Aug 1, 2019 at 6:51 PM Noah Misch wrote:
> vac_truncate_clog() instance 1 starts, considers segment ABCD eligible to
> unlink
> vac_truncate_clog() instance 2 starts, considers segment ABCD eligible to
> unlink
> vac_truncate_clog() instance 1 unlinks segment ABCD
> vac_truncate_clog() i
On Sat, Nov 2, 2019 at 10:38 AM Fabien COELHO wrote:
> Attached patch v4 does it.
Hi Fabien,
It looks like don't define sigint_interrupt_jmp and
sigint_interrupt_enabled on Windows, yet they are still declared and
referenced?
command.obj : error LNK2001: unresolved external symbol
sigint_interr
On Sat, Oct 19, 2019 at 05:02:01PM +0200, Adrien Nayrat wrote:
Hello,
This patch propose a new way to sample statement to logs.
As a reminder, this feature was committed in PG12[1] then reverted[2] after the
proposition of log_statement_sample_limit[3]
The first implementation added a new GUC
On Wed, Oct 16, 2019 at 6:49 PM Dave Cramer wrote:
> Here's an updated patch that addresses some of Andres' concerns specifically
> does not use strtok.
Hi Dave,
I think you need to s/strncasecmp/pg_strncasecmp/ to make this build on Windows.
https://ci.appveyor.com/project/postgresql-cfbot/po
Fabien COELHO writes:
>> I did experiment with trying to do that, but I couldn't get it to work,
>> even with the single version of libreadline I had at hand. It appears
>> to me that readline() starts by clearing the internal buffer. Even if
>> we could persuade it to work in a particular re
On Mon, Nov 4, 2019 at 12:11 PM Thomas Munro wrote:
> I guess I thought of that as a debugging feature and took it out
> because it was too verbose, but maybe it just needs to be controlled
> by the VERBOSE switch. Do you think we should put that back?
By which I mean: would you like to send a p
On Thu, Oct 31, 2019 at 5:24 AM Melanie Plageman
wrote:
> On Wed, Oct 23, 2019 at 12:30 AM Thomas Munro wrote:
>> Of course there are some more things that could be reported in a
>> similar way eventually, such as filter counters and hash join details.
>
> This made me think about other explain w
On Tue, Sep 10, 2019 at 11:43 AM Thomas Munro wrote:
> Rebased due to bitrot. Spotted one more place to use this, in
> src/backend/utils/adt/txid.c.
Rebased. I'm planning to commit this soon.
0001-Consolidate-code-that-makes-a-sorted-array-unique-v3.patch
Description: Binary data
On Tue, Oct 29, 2019 at 5:23 PM btfujiitkp wrote:
> > Thomas Munro writes:
> >> On Sun, Sep 1, 2019 at 5:04 PM Thomas Munro
> >> wrote:
> >>> Adding to CF.
> >
> >> Rebased. An OID clashed so re-roll the dice. Also spotted a typo.
> >
>
> I have some questions in this code.
Thanks for looking
[ redirecting to -hackers ]
I wrote:
> Yeah, it seems like a bad idea to override the user's choice to write
> a quote, even if one is not formally necessary. I propose the attached.
After further experimentation, I concluded that that patch is a bad idea;
it breaks a lot of cases that used to w
=?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= writes:
> Recently I got few times into situation where I was trying to find out what
> is blocking DELETE queries. Running EXPLAIN (even VERBOSE one) wasn't
> useful, since the reason was slow trigger (missing index on foreign key
> column). I had to create testin
On Sat, Nov 2, 2019 at 6:15 AM Tomas Vondra
wrote:
> On Fri, Nov 01, 2019 at 12:05:12PM +0300, Павел Ерёмин wrote:
> > Hi.
> > sorry for my English.
> > I want to once again open the topic of 64 bit transaction id. I did not
> > manage to find in the archive of the option that I want to di
Hi
Main goal of this patch is to avoid repeated calls of immutable/stable
functions.
This patch is against version 10.10.
I guess same logic could be implemented up till version 12.
--- src/include/nodes/execnodes.h 2019-08-05 23:16:54.0 +0200
+++ src/include/nodes/execnodes.h 2019-11-03 2
ne 3. 11. 2019 v 20:58 odesílatel Fabien COELHO
napsal:
>
> Hello Tom,
>
> >> I was suggesting something much simpler than rethinking readline
> handling.
> >> Does not mean that it is a good idea, but while testing the patch I
> would
> >> have liked the unfinished line to be in the current edit
Hello Tom,
I was suggesting something much simpler than rethinking readline handling.
Does not mean that it is a good idea, but while testing the patch I would
have liked the unfinished line to be in the current editing buffer,
basically as if I had not typed .
I did experiment with trying to
On Sun, Nov 03, 2019 at 02:17:15PM +0300, Павел Ерёмин wrote:
I completely agree with all of the above. Therefore, the proposed
mechanism may entail larger improvements (and not only VACUUM).
I think the best think you can do is try implementing this ...
I'm afraid the "improvements" essen
Hello!
Recently I got few times into situation where I was trying to find out what
is blocking DELETE queries. Running EXPLAIN (even VERBOSE one) wasn't
useful, since the reason was slow trigger (missing index on foreign key
column). I had to create testing entry and run EXPLAIN ANALYZE DELETE to
> On Wed, Sep 25, 2019 at 2:33 AM Dmitry Dolgov <9erthali...@gmail.com> wrote:
> v27-0001-Index-skip-scan.patch
>
> Some random thoughts on this:
Thanks a lot for the commentaries!
> * Is _bt_scankey_within_page() really doing the right thing within empty
> pages?
>
> It looks like you're accide
čt 10. 10. 2019 v 11:41 odesílatel Pavel Stehule
napsal:
> Hi
>
> minor change - replace heap_tuple_fetch_attr by detoast_external_attr.
>
>
similar update - heap_open, heap_close was replaced by table_open,
table_close
Regards
Pavel
schema_variables-20191103.patch
kerbrose khaled writes:
> I would like to update unaccent.rules file to support Arabic letters. so
> could someone help me or tell me how could I add such contribution. I
> attached the file including the modifications, only the last 4 lines.
Hi! I've got no objection to including Arabic in th
ilm...@ilmari.org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes:
> I just noticed that when contrib/seg was converted to V1 calling
> convention (commit 389bb2818f4), the PG_GETARG_SEG_P() macro got defined
> in terms of PG_GETARG_POINTER(). But it itself calls DatumGetPointer(),
> so shouldn
> On 3 Nov 2019, at 13:33, Pavel Stehule wrote:
>
> can be nice, if patch has some regress tests - it is good for memory
> refreshing what is target of patch.
With a suitably small work_mem constraint, it is possible to show the absence
of buffers resulting from the tuplestore. It’ll need some
Hi
ne 3. 11. 2019 v 12:51 odesílatel Dent John napsal:
> (And here’s aforementioned attachment… doh.)
>
can be nice, if patch has some regress tests - it is good for memory
refreshing what is target of patch.
Regards
Pavel
(And here’s aforementioned attachment… doh.)
pipeline-functionscan-v2.patch
Description: Binary data
I completely agree with all of the above. Therefore, the proposed mechanism may entail larger improvements (and not only VACUUM).I can offer the following solution.For VACUUM, create a hash table.VACUUM scanning the table sees that the version (tuple1) has t_ctid filled and refers to the address tu
Hello Andrey,
On 2019-11-02 12:30, Andrey Borodin wrote:
1 нояб. 2019 г., в 18:48, Alvaro Herrera
написал(а):
PFA two patches:
v4-0001-Use-memcpy-in-pglz-decompression.patch (known as 'hacked' in
test_pglz extension)
v4-0001-Use-memcpy-in-pglz-decompression-for-long-matches.patch (known
as 'ha
Le 02/11/2019 à 08:31, Michael Paquier a écrit :
> On Fri, Nov 01, 2019 at 05:29:23PM +0100, Gilles Darold wrote:
>> I have attached a patch to the documentation that adds remote tables to
>> the list of objects where any operation prevent using a prepared
>> transaction, currently it is just notif
43 matches
Mail list logo
