ttached patch removes sql/twophase
from schedule file and add new type of regression test.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
ecpg_prepared_txns_test.patch
Description: Binary data
--
Sent via pgsql-hackers ma
On Wed, Mar 15, 2017 at 1:09 PM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> On Fri, 10 Mar 2017 20:08:42 +0900
> Masahiko Sawada <sawada.m...@gmail.com> wrote:
>
>> On Fri, Mar 10, 2017 at 3:58 PM, Jim Nasby <jim.na...@openscg.com> wrote:
>> >
Hi,
Attached fixes comment typos in snapbuild.c file.
Regards,
--
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
fix_small_typo_in_snapbuild.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Fri, Mar 10, 2017 at 3:58 PM, Jim Nasby <jim.na...@openscg.com> wrote:
> On 3/6/17 8:34 PM, Masahiko Sawada wrote:
>>
>> I don't think it can say "1 frozen pages" because the number of
>> skipped pages according to visibility map is always more than 32
&g
This can ensure that
pg_class.relfrozenxid is not advanced past opaque->bp.xact with
minimal pain. Even if the btree dead page is leaved, the subsequent
modification makes garbage on heap and then autovauum recycles that
page while index vacuuming(lazy_index_vacuum).
Regards,
--
Masahiko S
On Wed, Feb 8, 2017 at 12:04 AM, Fujii Masao wrote:
> On Tue, Feb 7, 2017 at 2:13 AM, Petr Jelinek
> wrote:
>> On 06/02/17 17:33, Fujii Masao wrote:
>>> On Sun, Feb 5, 2017 at 5:11 AM, Petr Jelinek
>>> wrote:
pg_subscription of ObjectProperty
array are not correct. These values should be set ACL_KIND_PUBLICATION
and ACL_KIND_SUBSCRIPTION instead of -1. Attached small patch fixes
this issue and adds regression test.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Soft
uot;
I've read the discussion so far but I didn't see the reason why you've
changed it to as a contrib module. Could you tell me about that? I
guess this feature would be more useful if provided as a core feature
and we need to discuss about syntax as Thomas mentioned.
Regards,
--
Masahiko
patch.
Thanks
Previous 002 patch lacked to add describing PREPARE TRANSACTION.
Attached updated 002 patch.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
002_ecpg_commit_rollback_prepared_doc_v2.patch
Description: Binary data
--
Sent via pg
On Sat, Mar 4, 2017 at 4:37 AM, Peter Geoghegan <p...@bowt.ie> wrote:
> On Fri, Mar 3, 2017 at 8:13 AM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>> Thank you for clarification. Let me check my understanding. IIUC,
>> skipping second index vacuum path (lazy_cleanup
faf54a849898d9be012ddfa8204cfeb57c
> Author: Simon Riggs <si...@2ndquadrant.com>
> Date: Fri Mar 3 19:18:25 2017 +0530
>
> Allow vacuums to report oldestxmin
Attached updated v2 patch.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open So
anged, 5 insertions(+), 4 deletions(-)
>
>
Should we change the example in vacuum.sgml file as well? Attached patch.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
fix_vacuum_example_in_doc.patch
Description: Binary data
--
Sent via pgsql-h
On Sun, Mar 5, 2017 at 12:14 PM, David Steele <da...@pgmasters.net> wrote:
> On 3/4/17 9:08 PM, Masahiko Sawada wrote:
>> On Sat, Mar 4, 2017 at 5:47 PM, Robert Haas <robertmh...@gmail.com> wrote:
>>> On Fri, Mar 3, 2017 at 9:50 PM, Masahiko Sawada <sawada.m..
On Sat, Mar 4, 2017 at 1:46 PM, Peter Eisentraut
<peter.eisentr...@2ndquadrant.com> wrote:
> On 3/3/17 13:58, Petr Jelinek wrote:
>> On 23/02/17 08:24, Masahiko Sawada wrote:
>>> Attached updated version patches. Please review these.
>>>
>>
>> T
On Sat, Mar 4, 2017 at 5:47 PM, Robert Haas <robertmh...@gmail.com> wrote:
> On Fri, Mar 3, 2017 at 9:50 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>> Yes, it's taking a time to update logic and measurement but it's
>> coming along. Also I'm working on
gt; to see something very soon. If not, I think marking this RWF is the
> best course of action.
>
Thank you for the remind. I've post new idea about this. After got
consensus about the design, I'm going to update the patch.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE COR
On Fri, Mar 3, 2017 at 11:01 PM, David Steele <da...@pgmasters.net> wrote:
> On 1/10/17 11:23 AM, Claudio Freire wrote:
>> On Tue, Jan 10, 2017 at 6:42 AM, Masahiko Sawada <sawada.m...@gmail.com>
>> wrote:
>>>> Does this work negate the other work t
I changed it to have a threshold. If my
understanding is correct, we can have a threshold that specifies the
fraction of the scanned pages by vacuum. If it's set 0.1,
lazy_scan_heap can do the second vacuum index only when 10% of table
is scanned. IOW, if 90% of table pages is skipped, which means
ocumentation doesn't mentioned about these at all. Attached 002
patch add description about these to documentation.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
002_ecpg_commit_rollback_prepared_doc.patch
Desc
On Thu, Mar 2, 2017 at 11:56 AM, vinayak
<pokale_vinayak...@lab.ntt.co.jp> wrote:
>
> On 2017/02/28 16:54, Masahiko Sawada wrote:
>
> I've created a wiki page[1] describing about the design and
> functionality of this feature. Also it has some examples of use case,
> so th
orrectly skipping pages that the
> second scan should have scanned.
Agreed.
And the patch looks good to me.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make c
server, why do we need to stop it in order to execute pg_rewind to the
standbys on backup center? I guess you don't need to stop the new
primary server by using --source-server option.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, Feb 15, 2017 at 3:11 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Mon, Feb 6, 2017 at 10:48 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Wed, Feb 1, 2017 at 8:25 PM, Robert Haas <robertmh...@gmail.com> wrote:
>>> On Mon, J
On Fri, Feb 24, 2017 at 1:30 AM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
> Hi all,
>
> The autovacuum reports the number of skipped frozen pages to the
> VACUUM output. But these information is not appeared by manual VACUUM.
> This information is useful for the use
ely empty.
CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s.
VACUUM
I'll register it to next CF.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
report_frozen_skipped_pages_v1.patch
Description: Binary data
--
Sent via pgsql-hackers
20, 2017 at 3:01 PM, Simon Riggs <si...@2ndquadrant.com> wrote:
>>>> On 20 February 2017 at 09:15, Amit Kapila <amit.kapil...@gmail.com> wrote:
>>>>> On Mon, Feb 20, 2017 at 7:26 AM, Masahiko Sawada <sawada.m...@gmail.com>
>>>>> wrote:
>>>&g
On Wed, Feb 22, 2017 at 2:17 AM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Wed, Feb 22, 2017 at 1:52 AM, Fujii Masao <masao.fu...@gmail.com> wrote:
>> On Tue, Feb 21, 2017 at 7:52 PM, Masahiko Sawada <sawada.m...@gmail.com>
>> wrote:
>>> On
e_size('pg_global')"
> - Read all GUCs
>
Thank you for working on this.
What about granting to the role to read other statistic views such as
pg_stat_replication and pg_stat_wal_receiver? Since these informations
can only be seen by superuser the for example monitoring and
clustering to
On Wed, Feb 22, 2017 at 1:52 AM, Fujii Masao <masao.fu...@gmail.com> wrote:
> On Tue, Feb 21, 2017 at 7:52 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Tue, Feb 21, 2017 at 3:42 AM, Fujii Masao <masao.fu...@gmail.com> wrote:
>>> On Thu, Fe
initialize reply_message in exec_replication_command like follows.
diff --git a/src/backend/replication/walsender.c
b/src/backend/replication/walsender.c
index ba506e2..01b54f6 100644
--- a/src/backend/replication/walsender.c
+++ b/src/backend/replication/walsender.c
@@ -1258,6 +1258,7 @@ exec_replication_com
On Tue, Feb 21, 2017 at 3:42 AM, Fujii Masao <masao.fu...@gmail.com> wrote:
> On Thu, Feb 16, 2017 at 11:40 AM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Thu, Feb 16, 2017 at 7:52 AM, Petr Jelinek
>> <petr.jeli...@2ndquadrant.com> wrote:
>>
On Mon, Feb 20, 2017 at 6:15 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> On Mon, Feb 20, 2017 at 7:26 AM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Fri, Feb 17, 2017 at 3:41 AM, Robert Haas <robertmh...@gmail.com> wrote:
>>> On Thu, F
On Mon, Feb 20, 2017 at 11:35 AM, Jim Nasby <jim.na...@bluetreble.com> wrote:
> On 2/19/17 7:56 PM, Masahiko Sawada wrote:
>>
>> The half-dead pages are never cleaned up if the ratio of pages
>> containing garbage is always lower than threshold. Also in gin index
&
On Fri, Feb 17, 2017 at 3:41 AM, Robert Haas <robertmh...@gmail.com> wrote:
> On Thu, Feb 16, 2017 at 6:17 AM, Simon Riggs <si...@2ndquadrant.com> wrote:
>> On 15 February 2017 at 08:07, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>>> It's a bug. Attached lat
On Thu, Feb 16, 2017 at 7:52 AM, Petr Jelinek
<petr.jeli...@2ndquadrant.com> wrote:
> On 15/02/17 06:43, Masahiko Sawada wrote:
>> On Tue, Feb 14, 2017 at 1:13 AM, Fujii Masao <masao.fu...@gmail.com> wrote:
>>> On Mon, Feb 13, 2017 at 4:05 PM, Masahiko Sawada <
======
>
>
Thank you for testing!
It's a bug. Attached latest version patch, which passed make check.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
skip_cleanup_indexdes_v2.patch
Description:
On Tue, Feb 14, 2017 at 1:13 AM, Fujii Masao <masao.fu...@gmail.com> wrote:
> On Mon, Feb 13, 2017 at 4:05 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Sat, Feb 11, 2017 at 8:18 PM, Petr Jelinek
>> <petr.jeli...@2ndquadrant.com> wrote:
>>
On Fri, Feb 10, 2017 at 8:01 PM, Kuntal Ghosh
<kuntalghosh.2...@gmail.com> wrote:
> On Wed, Jan 4, 2017 at 1:51 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>
>> Attached patch introduces new GUC parameter parameter
>> vacuum_cleanup_index_scale_facto
On Sat, Feb 11, 2017 at 8:18 PM, Petr Jelinek
<petr.jeli...@2ndquadrant.com> wrote:
> On 10/02/17 19:55, Masahiko Sawada wrote:
>> On Thu, Feb 9, 2017 at 12:44 AM, Petr Jelinek
>> <petr.jeli...@2ndquadrant.com> wrote:
>>> On 08/02/17 07:40, Masahiko Sawada wro
umber of skipped the frozen
pages even in manual vacuum verbose log.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Thu, Feb 9, 2017 at 12:44 AM, Petr Jelinek
<petr.jeli...@2ndquadrant.com> wrote:
> On 08/02/17 07:40, Masahiko Sawada wrote:
>> On Wed, Feb 8, 2017 at 9:01 AM, Michael Paquier
>> <michael.paqu...@gmail.com> wrote:
>>> On Wed, Feb 8, 2017 at 1:30 AM, Fujii
stood there is too many failure scenarios we need to
handle.
>> Also DROP SUBSCRIPTION should call CommitTransactionCommand() just
>> after removing the entry from pg_subscription, then connect to the publisher
>> and remove the replication slot.
>
> For consistency that may
fixes
this issue.
Please give me feedback.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
drop_subscription_and_rollback.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Wed, Feb 1, 2017 at 8:25 PM, Robert Haas <robertmh...@gmail.com> wrote:
> On Mon, Jan 30, 2017 at 2:30 AM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> "txn" can be used for abbreviation of "Transaction", so for example
>> pg_fdw_t
Hi,
I think "laucher" should be "launcher". Attached patch fixes it.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
fix_typo_launcher_c.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-ha
On Wed, Feb 1, 2017 at 11:55 PM, Claudio Freire <klaussfre...@gmail.com> wrote:
> On Wed, Feb 1, 2017 at 6:13 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>> On Wed, Feb 1, 2017 at 10:02 PM, Claudio Freire <klaussfre...@gmail.com>
>> wrote:
>>>
On Wed, Feb 1, 2017 at 10:02 PM, Claudio Freire <klaussfre...@gmail.com> wrote:
> On Wed, Feb 1, 2017 at 5:47 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>> Thank you for updating the patch.
>>
>> Whole patch looks good to me except for the following
On Tue, Jan 31, 2017 at 3:05 AM, Claudio Freire <klaussfre...@gmail.com> wrote:
> On Mon, Jan 30, 2017 at 5:51 AM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>>
>> * We are willing to use at most maintenance_work_mem (or perhaps
>> * autovacuum_
On Thu, Jan 26, 2017 at 5:11 AM, Claudio Freire <klaussfre...@gmail.com> wrote:
> On Wed, Jan 25, 2017 at 1:54 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> Thank you for updating the patch!
>>
>> + /*
>> +* Quickly rule out by low
On Mon, Jan 30, 2017 at 12:50 PM, Ashutosh Bapat
<ashutosh.ba...@enterprisedb.com> wrote:
> On Sat, Jan 28, 2017 at 8:41 PM, Peter Eisentraut
> <peter.eisentr...@2ndquadrant.com> wrote:
>> On 1/26/17 4:49 AM, Masahiko Sawada wrote:
>>> Sorry, I attached wrong vers
On Thu, Jan 26, 2017 at 6:04 PM, vinayak
<pokale_vinayak...@lab.ntt.co.jp> wrote:
> Hi Sawada-san,
>
> On 2017/01/26 16:51, Masahiko Sawada wrote:
>
> Thank you for reviewing!
>
> I think this is a bug of pg_fdw_resolver contrib module. I had
> forgot
On Tue, Jan 24, 2017 at 1:49 AM, Claudio Freire <klaussfre...@gmail.com> wrote:
> On Fri, Jan 20, 2017 at 6:24 AM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Thu, Jan 19, 2017 at 8:31 PM, Claudio Freire <klaussfre...@gmail.com>
>> wrote:
>>&g
tats->num_index_scans++;
/* Report that we are once again scanning the heap */
I think that we should do vacrelstats->dead_tuples.num_entries = 0 as
well in lazy_clear_dead_tuples(). Once the amount of dead tuples
reached to maintenance_work_mem, lazy_scan_heap can never fin
On Thu, Jan 19, 2017 at 4:04 PM, vinayak
<pokale_vinayak...@lab.ntt.co.jp> wrote:
>
> On 2017/01/16 17:35, Masahiko Sawada wrote:
>>
>> On Fri, Jan 13, 2017 at 3:48 PM, Masahiko Sawada <sawada.m...@gmail.com>
>> wrote:
>>>
>>> On Fri, Ja
calling this function.
>
Since autovacuum worker wakes up autovacuum launcher after launched
the autovacuum launcher could try to spawn worker process at high
frequently if you have database with very large table in it that has
just passed autovacuum_freeze_max_age.
autovacuum.c:L1605
/* wa
On Mon, Jan 16, 2017 at 6:27 PM, Fujii Masao <masao.fu...@gmail.com> wrote:
> On Mon, Jan 16, 2017 at 5:42 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> Hi,
>>
>> Attached patch fixes comment typos in condition_variable.c
>
> Seems the pat
Hi,
Attached patch fixes comment typos in condition_variable.c
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
fix_type_in_condition_variable_c.patch
Description: binary/octet-stream
--
Sent via pgsql-hackers mailing list (pgsql-hackers
e parts of this design that will help) for
> solving smaller problem and tone down the patch for the same.
>
Sorry for confuse you. I'm still focusing on solving only that
problem. What I was trying to say is that I think that supporting
PREPARED transaction involving foreign server is the me
On Thu, Jan 12, 2017 at 9:29 AM, Josh Berkus <j...@agliodbs.com> wrote:
> Hackers:
>
> For that reason, as of today, I am stepping down from the PostgreSQL
> Core Team.
>
Thank you for all your efforts!
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPOR
On Fri, Dec 23, 2016 at 1:49 AM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Fri, Dec 9, 2016 at 4:02 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>> On Fri, Dec 9, 2016 at 3:02 PM, vinayak <pokale_vinayak...@lab.ntt.co.jp>
>> wrote:
>>>
Hi,
Attached fixes comment typos in dsa.c.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
fix_typo_in_dsa_c.patch
Description: binary/octet-stream
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Mon, Jan 9, 2017 at 6:01 PM, Simon Riggs <si...@2ndquadrant.com> wrote:
> On 9 January 2017 at 08:48, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>
>> I had not considered necessity of dead lock detection support.
>
> It seems like a big potential win to sca
On Tue, Jan 10, 2017 at 3:46 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> On Mon, Jan 9, 2017 at 2:18 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>> On Sat, Jan 7, 2017 at 2:47 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
>>> On Fri, Jan
On Sat, Jan 7, 2017 at 7:18 AM, Claudio Freire <klaussfre...@gmail.com> wrote:
> On Fri, Jan 6, 2017 at 2:38 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>> table_size | indexes | parallel_degree | time
>> +-+-+
On Sat, Jan 7, 2017 at 2:47 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> On Fri, Jan 6, 2017 at 11:08 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Mon, Oct 3, 2016 at 11:00 AM, Michael Paquier
>> <michael.paqu...@gmail.com> wrote:
>>&
On Mon, Oct 3, 2016 at 11:00 AM, Michael Paquier
<michael.paqu...@gmail.com> wrote:
> On Fri, Sep 16, 2016 at 6:56 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> Yeah, I don't have a good solution for this problem so far.
>> We might need to i
://www.postgresql.org/message-id/MWHPR20MB142177B86D893C946FAFC9A4A18C0%40MWHPR20MB1421.namprd20.prod.outlook.com
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
cleanup_indexes_threshold_v1.patch
Description: binary/octet-stream
--
Sent via pgsql-hackers
mit though those priority values are not used at all.
> Users can see those priority values in pg_stat_replication.
> Isn't this confusing? If yes, it might be better to always assign 1 as
> the priority, for example.
>
>
> Any other?
>
Do we need to consider the sorting method an
On Thu, Dec 15, 2016 at 3:06 PM, Kyotaro HORIGUCHI
<horiguchi.kyot...@lab.ntt.co.jp> wrote:
> At Thu, 15 Dec 2016 14:20:53 +0900, Masahiko Sawada <sawada.m...@gmail.com>
> wrote in <cad21aodn73ac+o0mrwcs800leosmyp4ov7xvb0t0_4v5vcq...@mail.gmail.com>
>> On Thu, Dec
d compatibility, I'd personally do it
> fully, and have a list of standby names specified meaning a priority
> list.
>
>> So I'd like to propose to keep the backward compatibility fully for s_s_names
>> (i.e., both "standby_list" and "N (standby_list)" mean the
On Mon, Dec 12, 2016 at 9:52 PM, Fujii Masao <masao.fu...@gmail.com> wrote:
> On Mon, Dec 12, 2016 at 9:31 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Sat, Dec 10, 2016 at 5:17 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
>>> On Thu,
On Sat, Dec 10, 2016 at 5:17 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> On Thu, Dec 8, 2016 at 3:02 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>> On Thu, Dec 8, 2016 at 4:39 PM, Michael Paquier
>> <michael.paqu...@gmail.com> wrote:
>>> O
On Fri, Dec 9, 2016 at 3:02 PM, vinayak <pokale_vinayak...@lab.ntt.co.jp> wrote:
> On 2016/12/05 14:42, Ashutosh Bapat wrote:
>>
>> On Mon, Dec 5, 2016 at 11:04 AM, Haribabu Kommi
>> <kommi.harib...@gmail.com> wrote:
>>
>>
>> On Fri, Nov 11, 2016
hese algorithm takes
almost the same time. And current patch does simple thing. When we
need over 100 or 1000 replication node the optimization could be
required.
Attached latest v9 patch.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
diff -
s algorithm. Could you elaborate
this? It takes only O(n) times?
> By the way, the patch now
> conflicts on HEAD, it needs a refresh.
Thanks, I'll post the latest patch.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent v
On Tue, Dec 6, 2016 at 1:11 PM, Fujii Masao <masao.fu...@gmail.com> wrote:
> On Mon, Nov 28, 2016 at 8:03 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Sat, Nov 26, 2016 at 10:27 PM, Michael Paquier
>> <michael.paqu...@gmail.com> wrote:
>>&
On Mon, Dec 5, 2016 at 9:15 PM, Ashutosh Bapat
<ashutosh.ba...@enterprisedb.com> wrote:
> On Mon, Dec 5, 2016 at 4:44 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
>> Hi all,
>>
>> Is there any reason why the max values of
>> autovacuum_vacuum/analyze_s
ussion of this topic, one dead tuple per page throughout the whole
> table is a LOT worse than same number of dead tuples all on the same
> pages. You don't want to keep scanning large chunks of the heap
> because you're too lazy to visit the indexes.
>
> --
> Robert Haas
>
Hi all,
Is there any reason why the max values of
autovacuum_vacuum/analyze_scale_factor are 100.0? These max values are
defined since when the parameters has been introduced but I think that
1.0 is enough.
Patch attached.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
ble is large, and has about 40GB index files. is there anyway to
> make the vacuum freeze faster in this case?
I guess that there is no way.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hac
On Sat, Nov 26, 2016 at 10:27 PM, Michael Paquier
<michael.paqu...@gmail.com> wrote:
> On Tue, Nov 15, 2016 at 7:08 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> Attached latest version patch incorporated review comments. After more
>> thought, I agree an
ring (or clustering with minimal
lock like pg_repack/pg_reorg does) in most cases. And I'm not sure
that there are a lot of users who build only BRIN index on the table.
I think that many users want to build other indexes on same table
other columns.
Regards,
--
Masahiko Sawada
NIPPON TELEGR
. Other design is similar to current your
patch; the offset of the array of array and the offset of a
ItemPointerData array control current location, which are cleared
after finished reclaiming garbage on heap and index. And allocated
array is re-used by subsequent scanning heap.
Regards,
--
Ma
ess
> index scans may be performing less redundant writes when cleaning
> up/reclaiming index pages).
What value of maintenance_work_mem did you use for this test? Since
DeadTuplesSegment struct still stores array of ItemPointerData(6byte)
representing dead tuple I supposed that the frequency of
On Mon, Nov 14, 2016 at 5:39 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Tue, Nov 8, 2016 at 10:12 PM, Michael Paquier
> <michael.paqu...@gmail.com> wrote:
>> On Tue, Nov 8, 2016 at 12:25 AM, Masahiko Sawada <sawada.m...@gmail.com>
>> wrote:
On Tue, Nov 8, 2016 at 10:12 PM, Michael Paquier
<michael.paqu...@gmail.com> wrote:
> On Tue, Nov 8, 2016 at 12:25 AM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Tue, Oct 25, 2016 at 10:35 PM, Michael Paquier
>> <michael.paqu...@gmail.com> wrote:
&g
On Wed, Nov 2, 2016 at 9:22 PM, Ashutosh Bapat
<ashutosh.ba...@enterprisedb.com> wrote:
> On Mon, Oct 31, 2016 at 6:17 AM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> On Fri, Oct 28, 2016 at 3:19 AM, Robert Haas <robertmh...@gmail.com> wrote:
>>> On
ould still be able
> to provide lag estimates if a standby has been down for a while and
> was catching up, and this approach can't until it's caught up due to
> lack of buffered transient timestamps. Thoughts?
>
> I plan to post a new "causal reads" patch at some point w
On Tue, Oct 25, 2016 at 10:35 PM, Michael Paquier
<michael.paqu...@gmail.com> wrote:
> On Mon, Oct 17, 2016 at 4:00 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>> Attached latest patch.
>> Please review it.
>
> Okay, so let's move on with this patch...
On Mon, Nov 7, 2016 at 10:52 PM, Beena Emerson <memissemer...@gmail.com> wrote:
> Hello Sawada-san,
>
> On Mon, Nov 7, 2016 at 4:47 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>>
>> On Wed, Nov 2, 2016 at 3:57 PM, Beena Emerson <memiss
regate-interval but I
> think the one in sampling-rate is better:
>
> $ pgbench --log-prefix=chk -t 20
> log file prefix (--log-prefix) is allowed only when actually logging
> transactions
>
> pgbench --sampling-rate=1 -t 20
> log sampling (--sampling-rate) is allowed only when logging
i.e. use "pgbench_log" as a prefix
> - add --log-prefix=... (long option only) for changing this prefix
>
Thank you for reviewing this patch!
I agree. It's better to add the separated option to specify the prefix
of log file instead of changing the existing behaviour. Attached
la
visibility we have, the
atomic commit by 2PC is necessary feature. We can consider to have the
atomic commit feature that ha following functionalities.
* The local node is responsible for the transaction management among
relevant remote servers using 2PC.
* The local node has information about the
On Wed, Oct 26, 2016 at 2:51 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Fri, Oct 21, 2016 at 2:38 PM, Ashutosh Bapat
> <ashutosh.ba...@enterprisedb.com> wrote:
>> On Wed, Oct 19, 2016 at 9:17 PM, Robert Haas <robertmh...@gmail.com> wrote:
>>>
visibility we have, the
atomic commit by 2PC is necessary feature. We can consider to have the
atomic commit feature that ha following functionalities.
* The local node is responsible for the transaction management among
relevant remote servers using 2PC.
* The local node has information about the
to run pgbench repeatedly in script
and collects and analyze the result.
The one thing I concern is that this patch changes -l option so that
it requires argument.
But changing its behavior would be good rather than adding new option.
Please give me feedback.
Regards,
--
Masahiko Sawada
NIPPON
On Mon, Oct 17, 2016 at 10:04 PM, Kevin Grittner <kgri...@gmail.com> wrote:
> On Sun, Oct 16, 2016 at 9:26 PM, Masahiko Sawada <sawada.m...@gmail.com>
> wrote:
>
>> When I set old_snapshot_threshold = 0 I got error at step #3, which
>> means that the error
I don't think that this patch is worth to pursue any
further, so I'd like to withdraw this.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
action I think that It's not problem of providing consistent
>> view.
>
> 2PC doesn't guarantee this. For that you need other methods and
> protocols. We have discussed this before. [2]
>
At any rate, I think that it would confuse the user that there is no
guarantee that the latest data updated by prev
On Tue, Oct 11, 2016 at 4:18 PM, Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Wed, Sep 28, 2016 at 5:14 PM, Michael Paquier
> <michael.paqu...@gmail.com> wrote:
>> On Sat, Sep 24, 2016 at 5:37 PM, Masahiko Sawada <sawada.m...@gmail.com>
>> wrote:
>
401 - 500 of 730 matches
Mail list logo