Re: Global snapshots

similarities. Thank you for this work! As I can see, main development difficulties placed in other areas: CSN, resolver, global deadlocks, 2PC commit... I'm not lawyer too. But if we get remarks from the patent holders, we can rewrite our Clock-SI implementation. -- regards, Andrey Lepikhov Pos

Re: Asynchronous Append on postgres_fdw nodes.

As you can see, executor scans one input and doesn't tried to scan another. -- regards, Andrey Lepikhov Postgres Professional

Re: Asynchronous Append on postgres_fdw nodes.

foreign_2)) AS b; is async capable, but: SELECT * FROM ((SELECT * FROM foreign_1 LIMIT 10) UNION ALL (SELECT a FROM foreign_2 LIMIT 10)) AS b; doesn't async capable. The patch in attachment tries to improve this situation. -- regards, Andrey Lepikhov Postgres Professional

Re: [POC] Fast COPY FROM command for the table with foreign partitions

status = true; + } I'm afraid it's not intuitive what "status is true" means. I think copy_data_sent or copy_send_success would be better for the variable name. Agreed. renamed to 'OK'. In accordance with psql/copy.c. (17) + if (PQputCopyEnd(conn, statu

[PATCH] XLogReadRecord returns pointer to currently read page

nter to an internal xlog page. This patch fixes the defect. Previously, in all cases of using WAL this was not a problem. However if you plan to perform some decoding operations before returning the WAL record to the caller (this is my case), this can lead to bugs that are difficult to catch.

Re: [PATCH] XLogReadRecord returns pointer to currently read page

17.08.2018 08:55, Michael Paquier пишет: On Fri, Aug 17, 2018 at 08:47:15AM +0500, Andrey Lepikhov wrote: Previously, in all cases of using WAL this was not a problem. However if you plan to perform some decoding operations before returning the WAL record to the caller (this is my case

Re: [WIP] [B-Tree] Retail IndexTuple deletion

of skewness of access frequency to relation blocks. 3. The cleaner does not cause a decrease of performance. -- Andrey Lepikhov Postgres Professional https://postgrespro.com The Russian Postgres Company >From b465357b8a884cac3b503ad171976d3afd31f574 Mon Sep 17 00:00:00 2001 From: "Andrey

Re: [WIP] [B-Tree] Retail IndexTuple deletion

And background worker patch in attachment. 05.09.2018 15:25, Andrey Lepikhov пишет: Hi, I prepared next version of Background worker (cleaner) based on a retail indextuple deletion patch. This version shows stable behavior on regression tests and pgbench workloads. In this version: 1. Only

Clarification of nodeToString() use cases

e attachment). [1] https://github.com/postgrespro/aqo [2] hash.c, line 55. [3] outfuncs.c, line 3312. -- Andrey Lepikhov Postgres Professional https://postgrespro.com The Russian Postgres Company >From 26bfe91a4901b3b342e1b3ed58252ac750773207 Mon Sep 17 00:00:00 2001 From: "Andrey V. Lepikhov&

Re: XMLNAMESPACES (was Re: Clarification of nodeToString() use cases)

16.09.2018 23:05, Tom Lane writes: Andrey Lepikhov writes: The reason is: parse tree node for XMLNAMESPACES clause has null pointer in the case of DEFAULT namespace (the pointer will be initialized at executor on the first call). My immediate reaction is that somebody made a bad decision

Re: [WIP] [B-Tree] Retail IndexTuple deletion

gresql.org/message-id/CAH2-WzkfK=jvhjkd17tldvsfb6psdutt5wyit8dg+-ufc+r...@mail.gmail.com -- Andrey Lepikhov Postgres Professional https://postgrespro.com The Russian Postgres Company >From 99c9bc340a730a85328549165ae8023a0716e147 Mon Sep 17 00:00:00 2001 From: "Andrey V. Lepikhov" Da

Re: Making all nbtree entries unique by having heap TIDs participate in comparisons

* Do more traditional benchmarking. * Add pg_upgrade support. * Simplify _bt_findsplitloc() logic. [1] https://postgr.es/m/cah2-wzmf0fvvhu+sszpgw4qe9t--j_dmxdx3it5jcdb8ff2...@mail.gmail.com -- Andrey Lepikhov Postgres Professional https://postgrespro.com The Russian Postgres Company

Re: [WIP] [B-Tree] Retail IndexTuple deletion

1 -> 10 tuples vacuumed. Time measured in ms. So, quick strategy can be used in a vacuum process effectively up to 1-2% of DEAD tuples in a relation. -- Andrey Lepikhov Postgres Professional https://postgrespro.com The Russian Postgres Company >From a5664f6fa42f615d1fb46250ac61aa9a

Re: Making all nbtree entries unique by having heap TIDs participate in comparisons

estigation and benchmarking. Now benchmarking is not clear. Possible performance degradation from TID ordering interfere with positive effects from the optimizations in non-trivial way. -- Andrey Lepikhov Postgres Professional https://postgrespro.com The Russian Postgres Company

<    1   2   3