Hello
I found a comment typo in xlogprefetcher.c.
Any thoughts?
--- a/src/backend/access/transam/xlogprefetcher.c
+++ b/src/backend/access/transam/xlogprefetcher.c
@@ -19,7 +19,7 @@
* avoid a second buffer mapping table lookup.
*
* Currently, only the main fork is considered for prefetching
Hello,
This patch status is already returned with feedback.
However, I've applied this patch on 27b77ecf9f and tested so report it.
make installcheck-world is passed.
However, when I promote the standby server and update on the new primary server,
apply worker could not start logical replication
Hello,
I run vcregeress plcheck on Windows Server 2016 with python 3.11.0a3 and python
3.9.7 which are installed using installer.
All tests are passed. I'm not familiar with PL/Python but I think it's good.
regards, sho kato
>I'm moving to another company from July 1st. I may possibly not be allowed to
>do open source activities there, so let me say >goodbye once. Thank you all
>for your help. I really enjoyed learning PostgreSQL and participating in its
>development.
Thank you for everything, Tsunakawa-san.
Goo
On Wednesday, August 5, 2020 9:43 AM I wrote:
> I'll report the result before the end of August .
I test v2-0001-build-partdesc-memcxt.patch at 9a9db08ae4 and it is ok.
Firstly, I execute ALTER TABLE ADD CONSTRAINT FOREIGN KEY on the table which
has 8k tables.
This query execution completes in a
On Tuesday, July 14, 2020 11:29 PM, Daniel Fustafsson wrote:
>Are you able to test Alvaros latest patch to see if that solves the originally
>reported problem, so that we can reach >closure on this item during the
>commitfest?
Sorry for the too late replay. I missed this mail.
And, thanks for w
>So, after looking at these functions and modifying this patch, I would like to
>add this patch to the next
I updated this patch and registered for the next CF .
https://commitfest.postgresql.org/29/2654/
regards,
sho kato
pruning-with-row-wise-comparison-v2.patch
Description: pruning-with-r
Amit-san
Friday, July 10, 2020 10:00 AM, Amit Langote wrote:
>Speaking of which, I hope that Kato-san has looked at functions
>match_rowcompare_to_indexcol(), expand_indexqual_rowcompare(), etc. in
>indxpath.c as starting points >for the code to match RowCompares to partition
>keys.
Hmm, I did
Hi,
I made a patch that enable partition pruning using row-wise comparison.
Please review and comment on this patch.
regards,
sho kato
> -Original Message-
> From: kato-...@fujitsu.com
> Sent: Wednesday, July 8, 2020 10:33 AM
> To: 'Etsuro Fujita'
> C
-Original Message-
> From: Fujii Masao
> Sent: Wednesday, July 8, 2020 3:20 PM
> To: Kato, Sho/加藤 翔 ; 'Amit Langote'
>
> Cc: Etsuro Fujita ; PostgreSQL-development
>
> Subject: Re: Performing partition pruning using row value
>
>
>
> On 2020/07
ed to hear this reason.
Regards,
Sho kato
> -Original Message-
> From: Amit Langote
> Sent: Wednesday, July 8, 2020 11:53 AM
> To: Kato, Sho/加藤 翔
> Cc: Etsuro Fujita ; PostgreSQL-development
>
> Subject: Re: Performing partition pruning using row value
>
> Ka
POC that allows row-wise comparison with partition-pruning.
Regards,
sho kato
> -Original Message-
> From: Etsuro Fujita
> Sent: Tuesday, July 7, 2020 6:31 PM
> To: Kato, Sho/加藤 翔
> Cc: PostgreSQL-development
> Subject: Re: Performing partition pruning using row val
Hello
I would like to ask about the conditions under which partition pruning is
performed.
In PostgreSQL 12, when I executed following SQL, partition pruning is not
performed.
postgres=# explain select * from a where (c1, c2) < (99, 99);
QUERY PLAN
---
Hello
To benchmark with tpcb model, I tried to create a foreign key in the
partitioned history table, but backend process killed by OOM.
the number of partitions is 8192. I tried in master(commit: ad4b7aeb84).
I did the same thing in another server which has 200GB memory, but creating
foreign k
14 matches
Mail list logo
