Re: [HACKERS] Behavior of a pg_trgm index for 2 (or 3) character LIKE queries

2013-05-30 Thread Sawada Masahiko
2013/5/31 Amit Langote amitlangot...@gmail.com On Thu, May 30, 2013 at 11:47 PM, Robert Haas robertmh...@gmail.com wrote: On Wed, May 29, 2013 at 10:51 PM, Amit Langote amitlangot...@gmail.com wrote: So, it appears, for search strings consisting of 2 (or 3) characters, trigrams can not

Re: [HACKERS] Behavior of a pg_trgm index for 2 (or 3) character LIKE queries

2013-05-31 Thread Sawada Masahiko
On Fri, May 31, 2013 at 11:16 AM, Amit Langote amitlangot...@gmail.com wrote: On Fri, May 31, 2013 at 4:25 AM, Alexander Korotkov aekorot...@gmail.com wrote: On Thu, May 30, 2013 at 12:49 PM, Sawada Masahiko sawada.m...@gmail.com wrote: following emails are discussed about partial match

Re: [HACKERS] Patch for fail-back without fresh backup

2013-06-15 Thread Sawada Masahiko
changes aren't done before WAL replicated. -- Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Patch for fail-back without fresh backup

2013-06-15 Thread Sawada Masahiko
On Sat, Jun 15, 2013 at 10:34 PM, Amit kapila amit.kap...@huawei.com wrote: On Saturday, June 15, 2013 1:19 PM Sawada Masahiko wrote: On Fri, Jun 14, 2013 at 10:15 PM, Amit Kapila amit.kap...@huawei.com wrote: On Friday, June 14, 2013 2:42 PM Samrat Revagade wrote: Hello, We have already

Re: [HACKERS] Patch for fail-back without fresh backup

2013-06-17 Thread Sawada Masahiko
On Sun, Jun 16, 2013 at 2:00 PM, Amit kapila amit.kap...@huawei.com wrote: On Saturday, June 15, 2013 8:29 PM Sawada Masahiko wrote: On Sat, Jun 15, 2013 at 10:34 PM, Amit kapila amit.kap...@huawei.com wrote: On Saturday, June 15, 2013 1:19 PM Sawada Masahiko wrote: On Fri, Jun 14, 2013 at 10

Re: [HACKERS] Patch for fail-back without fresh backup

2013-06-18 Thread Sawada Masahiko
On Tuesday, June 18, 2013, Amit Kapila wrote: On Tuesday, June 18, 2013 12:18 AM Sawada Masahiko wrote: On Sun, Jun 16, 2013 at 2:00 PM, Amit kapila amit.kap...@huawei.comjavascript:; wrote: On Saturday, June 15, 2013 8:29 PM Sawada Masahiko wrote: On Sat, Jun 15, 2013 at 10:34 PM

Re: [HACKERS] Patch for fail-back without fresh backup

2013-06-19 Thread Sawada Masahiko
On Tuesday, June 18, 2013, Amit Kapila wrote: On Tuesday, June 18, 2013 12:18 AM Sawada Masahiko wrote: On Sun, Jun 16, 2013 at 2:00 PM, Amit kapila amit.kap...@huawei.comjavascript:; wrote: On Saturday, June 15, 2013 8:29 PM Sawada Masahiko wrote: On Sat, Jun 15, 2013 at 10:34 PM

Re: [HACKERS] Patch for fail-back without fresh backup

2013-06-24 Thread Sawada Masahiko
wal_sender_timeout = 30 [Server] standby_name = 'slave2' synchronous_transfer = all wal_sender_timeout = 50 --- there are discussions about such ini file in past. if so, we can set each parameter to each standby. please give me feedback. Regards, --- Sawada Masahiko -- Sent via pgsql

Re: [HACKERS] Patch for fail-back without fresh backup

2013-06-25 Thread Sawada Masahiko
On Tue, Jun 25, 2013 at 12:19 PM, Pavan Deolasee pavan.deola...@gmail.com wrote: On Mon, Jun 24, 2013 at 7:17 PM, Sawada Masahiko sawada.m...@gmail.com wrote: [Server] standby_name = 'slave1' synchronous_transfer = commit wal_sender_timeout = 30 [Server

Re: [HACKERS] Patch for fail-back without fresh backup

2013-06-27 Thread Sawada Masahiko
On Mon, Jun 24, 2013 at 10:47 PM, Sawada Masahiko sawada.m...@gmail.com wrote: 1. synchronous standby and make same as failback safe standby 2. asynchronous standby and make same as failback safe standby in above case, adding new parameter might be meaningless. but I think that we should

Re: [HACKERS] Patch for fail-back without fresh backup

2013-06-27 Thread Sawada Masahiko
, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Patch for fail-back without fresh backup

2013-07-02 Thread Sawada Masahiko
On Tue, Jul 2, 2013 at 2:45 PM, Amit Kapila amit.kap...@huawei.com wrote: On Friday, June 28, 2013 10:41 AM Sawada Masahiko wrote: On Wed, Jun 26, 2013 at 1:40 PM, Amit Kapila amit.kap...@huawei.com wrote: On Tuesday, June 25, 2013 10:23 AM Amit Langote wrote: Hi, So our proposal

Re: [HACKERS] Patch for fail-back without fresh backup

2013-07-07 Thread Sawada Masahiko
safe standby 2. we have not measure performance yet. we need to measure perfomance. please give me your feedback. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [HACKERS] Patch for fail-back without fresh backup

2013-07-07 Thread Sawada Masahiko
On Sun, Jul 7, 2013 at 4:19 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Mon, Jun 17, 2013 at 8:48 PM, Simon Riggs si...@2ndquadrant.com wrote: On 17 June 2013 09:03, Pavan Deolasee pavan.deola...@gmail.com wrote: I agree. We should probably find a better name for this. Any suggestions

Re: [HACKERS] Patch for fail-back without fresh backup

2013-07-09 Thread Sawada Masahiko
On Sun, Jul 7, 2013 at 4:27 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sun, Jul 7, 2013 at 4:19 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Mon, Jun 17, 2013 at 8:48 PM, Simon Riggs si...@2ndquadrant.com wrote: On 17 June 2013 09:03, Pavan Deolasee pavan.deola...@gmail.com

Re: [HACKERS] Patch for fail-back without fresh backup

2013-07-11 Thread Sawada Masahiko
On Tue, Jul 9, 2013 at 11:45 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sun, Jul 7, 2013 at 4:27 PM, Sawada Masahiko sawada.m...@gmail.com wrote: I found a bug which occurred when we do vacuum, and have fixed it. yesterday (8th July) Improve scalability of WAL insertions patch

Re: [HACKERS] Using ini file to setup replication

2013-07-22 Thread Sawada Masahiko
(e.g., wal_sender_timeout) is not set in configure file(or postgresql,conf) like above, what value should we set value to parameter? and how we handle originally wal_sender_timeout? will it leave? or delete? Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Using ini file to setup replication

2013-07-23 Thread Sawada Masahiko
as option of overwrite. of course to support this approach, it needs to use the patch which Andres suggested, and server should be able to handle toke which is two or mote separated by a dot. so we would like to help this approach. Regards, Sawada Masahiko -- Sent via pgsql-hackers

[HACKERS] Condition to become the standby mode.

2013-07-25 Thread Sawada Masahiko
://www.postgresql.org/message-id/CAF8Q-Gy7xa60HwXc0MKajjkWFEbFDWTG=ggyu1kmt+s2xcq...@mail.gmail.com -- Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Parsing bool type value

2013-08-20 Thread Sawada Masahiko
value in parse_bool_with_len() function. Should we deny the of value as bool type value? Regards, --- Sawada Masahiko parse_bool_with_len.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Parsing bool type value

2013-08-20 Thread Sawada Masahiko
On Tue, Aug 20, 2013 at 11:53 PM, Amit Kapila amit.kapil...@gmail.com wrote: On Tue, Aug 20, 2013 at 1:11 PM, Sawada Masahiko sawada.m...@gmail.com wrote: Hi all, Taking a look at PostgreSQL HEAD today, I noticed that currently PostgreSQL allows of value as bool type value. So user can

[HACKERS] Behaviour of take over the synchronous replication

2013-08-23 Thread Sawada Masahiko
missing? Please give me feedback. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-24 Thread Sawada Masahiko
On Sat, Aug 24, 2013 at 3:14 AM, Josh Berkus j...@agliodbs.com wrote: On 08/23/2013 12:42 AM, Sawada Masahiko wrote: in case (a), those priority is clear. So I think that re-taking over is correct behaviour. OHOT, in case (b), even if AAA and BBB are set same priority, AAA server steals SYNC

Re: [HACKERS] Patch for fail-back without fresh backup

2013-08-25 Thread Sawada Masahiko
On Sat, Aug 24, 2013 at 11:38 PM, Peter Eisentraut pete...@gmx.net wrote: On Thu, 2013-07-11 at 23:42 +0900, Sawada Masahiko wrote: please find the attached patch. Please fix these compiler warnings: xlog.c:3117:2: warning: implicit declaration of function ‘SyncRepWaitForLSN’ [-Wimplicit

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-27 Thread Sawada Masahiko
On Sun, Aug 25, 2013 at 3:21 PM, Amit Kapila amit.kapil...@gmail.com wrote: On Sat, Aug 24, 2013 at 2:46 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sat, Aug 24, 2013 at 3:14 AM, Josh Berkus j...@agliodbs.com wrote: On 08/23/2013 12:42 AM, Sawada Masahiko wrote: in case (a), those

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-27 Thread Sawada Masahiko
if user execute query, master server doesn't freeze commits When 'AAA' walsender state become 'streaming', 'AAA' becomes preferred sync standby again. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-30 Thread Sawada Masahiko
On Wed, Aug 28, 2013 at 10:59 PM, Amit Kapila amit.kapil...@gmail.com wrote: On Tue, Aug 27, 2013 at 4:51 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sun, Aug 25, 2013 at 3:21 PM, Amit Kapila amit.kapil...@gmail.com wrote: On Sat, Aug 24, 2013 at 2:46 PM, Sawada Masahiko sawada.m

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-12 Thread Sawada Masahiko
] Sorry I forgot fix it. I have attached the patch which I modified. Regards, --- Sawada Masahiko synchronous_transfer_v6.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-17 Thread Sawada Masahiko
, failback safe standby is the same as SYNC replication standby. User can set synchronous_transfer in only master side. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-17 Thread Sawada Masahiko
On Wed, Sep 18, 2013 at 11:45 AM, Fujii Masao masao.fu...@gmail.com wrote: On Wed, Sep 18, 2013 at 10:35 AM, Sawada Masahiko sawada.m...@gmail.com wrote: On Tue, Sep 17, 2013 at 9:52 PM, Fujii Masao masao.fu...@gmail.com wrote: I set up synchronous replication with synchronous_transfer = all

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-17 Thread Sawada Masahiko
On Wed, Sep 18, 2013 at 1:05 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Wed, Sep 18, 2013 at 11:45 AM, Fujii Masao masao.fu...@gmail.com wrote: On Wed, Sep 18, 2013 at 10:35 AM, Sawada Masahiko sawada.m...@gmail.com wrote: On Tue, Sep 17, 2013 at 9:52 PM, Fujii Masao masao.fu

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-18 Thread Sawada Masahiko
On Wed, Sep 18, 2013 at 11:45 AM, Fujii Masao masao.fu...@gmail.com wrote: On Wed, Sep 18, 2013 at 10:35 AM, Sawada Masahiko sawada.m...@gmail.com wrote: On Tue, Sep 17, 2013 at 9:52 PM, Fujii Masao masao.fu...@gmail.com wrote: I set up synchronous replication with synchronous_transfer = all

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-19 Thread Sawada Masahiko
On Thu, Sep 19, 2013 at 12:25 PM, Fujii Masao masao.fu...@gmail.com wrote: On Thu, Sep 19, 2013 at 11:48 AM, Sawada Masahiko sawada.m...@gmail.com wrote: I attached the patch which I have modified. Thanks for updating the patch! Here are the review comments: Thank you for reviewing! I

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-19 Thread Sawada Masahiko
On Thu, Sep 19, 2013 at 7:32 PM, Fujii Masao masao.fu...@gmail.com wrote: On Thu, Sep 19, 2013 at 7:07 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Thu, Sep 19, 2013 at 12:25 PM, Fujii Masao masao.fu...@gmail.com wrote: On Thu, Sep 19, 2013 at 11:48 AM, Sawada Masahiko sawada.m

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-22 Thread Sawada Masahiko
synchronous_commit. Regards, --- Sawada Masahiko synchronous_transfer_v10.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-27 Thread Sawada Masahiko
'on', the master wait for data flush eve if user sets synchronous_commit to 'local' or 'off'. For example, when user want to do transaction early, user can't do this. we leave the such situation as constraint? Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Patch for fail-back without fresh backup

2013-09-27 Thread Sawada Masahiko
On Fri, Sep 27, 2013 at 5:18 PM, Pavan Deolasee pavan.deola...@gmail.com wrote: On Fri, Sep 27, 2013 at 1:28 PM, Sawada Masahiko sawada.m...@gmail.com wrote: Thank you for comment. I think it is good simple idea. In your opinion, if synchronous_transfer is set 'all

Re: [HACKERS] Patch for fail-back without fresh backup

2013-10-03 Thread Sawada Masahiko
On Fri, Sep 27, 2013 at 6:44 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Fri, Sep 27, 2013 at 5:18 PM, Pavan Deolasee pavan.deola...@gmail.com wrote: On Fri, Sep 27, 2013 at 1:28 PM, Sawada Masahiko sawada.m...@gmail.com wrote: Thank you for comment. I think it is good simple

Re: [HACKERS] Patch for fail-back without fresh backup

2013-10-08 Thread Sawada Masahiko
. + */ +if (SyncTransRequested()) +SyncRepWaitForLSN(lsn, true, true); If smgr_redo() is called only during recovery, SyncRepWaitForLSN() doesn't need to be called here. Thank you for info. I have removed it at smgr_redo(). Regards, --- Sawada Masahiko

Re: [HACKERS] Patch for fail-back without fresh backup

2013-10-09 Thread Sawada Masahiko
On Tue, Oct 8, 2013 at 6:37 PM, Pavan Deolasee pavan.deola...@gmail.com wrote: On Tue, Oct 8, 2013 at 2:33 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Fri, Oct 4, 2013 at 4:32 PM, Fujii Masao masao.fu...@gmail.com wrote: I attached the v12 patch which have modified based on above

Re: [HACKERS] Patch for fail-back without fresh backup

2013-10-09 Thread Sawada Masahiko
On Tue, Oct 8, 2013 at 6:46 PM, Andres Freund and...@2ndquadrant.com wrote: On 2013-10-08 15:07:02 +0530, Pavan Deolasee wrote: On Tue, Oct 8, 2013 at 2:33 PM, Sawada Masahiko sawada.m...@gmail.comwrote: On Fri, Oct 4, 2013 at 4:32 PM, Fujii Masao masao.fu...@gmail.com wrote: I attached

Re: [HACKERS] Patch for fail-back without fresh backup

2013-10-21 Thread Sawada Masahiko
to worry about ? Any strong objections to this idea or any other stow stopper for pg_rewind itself ? -- Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql

Re: [HACKERS] Patch for fail-back without fresh backup

2013-10-24 Thread Sawada Masahiko
in synchronous ( of course when configuring sync replication)? I am concerned that it lead performance overhead with such as executing SELECT or auto vacuum. especially, when two servers are in far location. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Patch for fail-back without fresh backup

2013-11-02 Thread Sawada Masahiko
discussed..) Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] The number of character limitation of custom script on pgbench

2013-11-13 Thread Sawada Masahiko
not know why function of custom script is not work fine. It look as just error of SQL to user. So I'm thinking following solution. (1) to increase buffer size (2) to change to variable buffer size (3) to return ERROR with information Thought? Regards, --- Sawada Masahiko -- Sent via

Re: [HACKERS] The number of character limitation of custom script on pgbench

2013-11-13 Thread Sawada Masahiko
On Wed, Nov 13, 2013 at 10:27 PM, Tom Lane t...@sss.pgh.pa.us wrote: Peter Eisentraut pete...@gmx.net writes: On 11/13/13, 6:18 AM, Sawada Masahiko wrote: The function of custom script of pgbench allows only BUFSIZ (i.g.,1024byte) or less as length of a SQL. So I'm thinking following

[HACKERS] Logging WAL when updating hintbit

2013-11-13 Thread Sawada Masahiko
...@mail.gmail.com Regards, --- Sawada Masahiko log_hint_bit_wal_v1.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-14 Thread Sawada Masahiko
On Thu, Nov 14, 2013 at 3:53 PM, Michael Paquier michael.paqu...@gmail.com wrote: On Thu, Nov 14, 2013 at 3:02 PM, Sawada Masahiko sawada.m...@gmail.com wrote: I attached patch adds new wal_level 'all'. If wal_level is set 'all', the server logs WAL not only when wal_level is set

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-15 Thread Sawada Masahiko
On Thu, Nov 14, 2013 at 7:51 PM, Florian Weimer fwei...@redhat.com wrote: On 11/14/2013 07:02 AM, Sawada Masahiko wrote: I attached patch adds new wal_level 'all'. Shouldn't this be a separate setting? It's useful for storage which requires rewriting a partially written sector before

Re: [HACKERS] The number of character limitation of custom script on pgbench

2013-11-15 Thread Sawada Masahiko
On Wed, Nov 13, 2013 at 10:27 PM, Tom Lane t...@sss.pgh.pa.us wrote: Peter Eisentraut pete...@gmx.net writes: On 11/13/13, 6:18 AM, Sawada Masahiko wrote: The function of custom script of pgbench allows only BUFSIZ (i.g.,1024byte) or less as length of a SQL. So I'm thinking following

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-17 Thread Sawada Masahiko
On Fri, Nov 15, 2013 at 11:33 PM, Peter Eisentraut pete...@gmx.net wrote: On 11/14/13, 1:02 AM, Sawada Masahiko wrote: I attached patch adds new wal_level 'all'. Compiler warning: pg_controldata.c: In function ‘wal_level_str’: pg_controldata.c:72:2: warning: enumeration value ‘WAL_LEVEL_ALL

Re: [HACKERS] [PATCH] pg_basebackup: progress report max once per second

2013-11-17 Thread Sawada Masahiko
: connection to client lost Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-19 Thread Sawada Masahiko
On Tue, Nov 19, 2013 at 3:54 PM, KONDO Mitsumasa kondo.mitsum...@lab.ntt.co.jp wrote: (2013/11/15 19:27), Sawada Masahiko wrote: On Thu, Nov 14, 2013 at 7:51 PM, Florian Weimer fwei...@redhat.com wrote: On 11/14/2013 07:02 AM, Sawada Masahiko wrote: I attached patch adds new wal_level 'all

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-20 Thread Sawada Masahiko
On Wed, Nov 20, 2013 at 9:19 PM, Dilip kumar dilip.ku...@huawei.com wrote: On 19 November 2013 22:19, Sawada Masahiko Wrote Thanks! I took it wrong. I think that there are quite a few difference amount of WAL. Did you test about amount of WAL size in your patch? Not yet. I will do

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-21 Thread Sawada Masahiko
On Thu, Nov 21, 2013 at 8:59 PM, Dilip kumar dilip.ku...@huawei.com wrote: On 20 November 2013 22:12, Sawada Masahiko Wrote 1. Patch applies cleanly to master HEAD. 2. No Compilation Warning. 3. It works as per the patch expectation. Some Suggestion: 1. Add new WAL level (all

Re: [HACKERS] segfault with contrib lo

2013-11-23 Thread Sawada Masahiko
suggestion that error message shows name of trigger. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-25 Thread Sawada Masahiko
'enable_logging_hintbit'. It works same as previous patch, just independence from wal_level and name is changed. One changed behave is that it doesn't work together with 'minimal' wal_level. Regards, --- Sawada Masahiko log_hint_bit_wal_v3.patch Description: Binary data -- Sent via pgsql

[HACKERS] psql shows line number

2013-11-26 Thread Sawada Masahiko
. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] psql shows line number

2013-11-26 Thread Sawada Masahiko
On Tue, Nov 26, 2013 at 9:23 PM, Marko Tiikkaja ma...@joh.to wrote: On 11/26/13 1:05 PM, Sawada Masahiko wrote: When I execute query which contains error, the server returns error with line number. ERROR: relation hoge does not exist LINE 35: hoge; But when query is long, I was not sure

Re: [HACKERS] psql shows line number

2013-11-26 Thread Sawada Masahiko
2013/11/26 22:24 Pavel Stehule pavel.steh...@gmail.com: 2013/11/26 Sawada Masahiko sawada.m...@gmail.com On Tue, Nov 26, 2013 at 9:23 PM, Marko Tiikkaja ma...@joh.to wrote: On 11/26/13 1:05 PM, Sawada Masahiko wrote: When I execute query which contains error, the server returns error

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-26 Thread Sawada Masahiko
On Mon, Nov 25, 2013 at 9:02 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sun, Nov 24, 2013 at 6:02 AM, Jeff Davis pg...@j-davis.com wrote: On Tue, 2013-11-19 at 11:42 -0500, Robert Haas wrote: My take is that configuration options should be used to serve different use cases. One thing

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-26 Thread Sawada Masahiko
On Wed, Nov 27, 2013 at 2:28 AM, Tom Lane t...@sss.pgh.pa.us wrote: Peter Eisentraut pete...@gmx.net writes: On 11/25/13, 7:02 AM, Sawada Masahiko wrote: I attached the new version patch which adds separated parameter 'enable_logging_hintbit'. Let's not add more parameters named enable_

Re: [HACKERS] Logging WAL when updating hintbit

2013-11-28 Thread Sawada Masahiko
On Wed, Nov 27, 2013 at 11:22 AM, Michael Paquier michael.paqu...@gmail.com wrote: On Wed, Nov 27, 2013 at 11:04 AM, Sawada Masahiko sawada.m...@gmail.com wrote: Thank you for feedback. I attached the v4 patch which have modified. Just name changed to 'wal_log_hintbtis'. Few typos

Re: [HACKERS] Logging WAL when updating hintbit

2013-12-02 Thread Sawada Masahiko
it occur? I think pg_rewind can disagree to rewind if log_hint_bits is changed to 'OFF'. Is this not enough? Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Logging WAL when updating hintbit

2013-12-03 Thread Sawada Masahiko
On Tue, Dec 3, 2013 at 4:28 PM, Michael Paquier michael.paqu...@gmail.com wrote: On Tue, Dec 3, 2013 at 3:30 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Tue, Dec 3, 2013 at 12:02 PM, Michael Paquier michael.paqu...@gmail.com wrote: Indeed, I forgot this code path. Completing

Re: [HACKERS] Logging WAL when updating hintbit

2013-12-03 Thread Sawada Masahiko
On Tue, Dec 3, 2013 at 5:34 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Tue, Dec 3, 2013 at 4:28 PM, Michael Paquier michael.paqu...@gmail.com wrote: On Tue, Dec 3, 2013 at 3:30 PM, Sawada Masahiko sawada.m...@gmail.com wrote: After more thinking... Before performing a rewind

Re: [HACKERS] Logging WAL when updating hintbit

2013-12-12 Thread Sawada Masahiko
On Fri, Dec 13, 2013 at 1:51 PM, Dilip kumar dilip.ku...@huawei.com wrote: On 04 December 2013, Sawada Masahiko Wrote I attached the patch which have modified based on Robert suggestion, and fixed typo. I have reviewed the modified patch and I have some comments.. 1. Patch need

Re: [HACKERS] Logging WAL when updating hintbit

2013-12-13 Thread Sawada Masahiko
On Fri, Dec 13, 2013 at 5:49 PM, Dilip kumar dilip.ku...@huawei.com wrote: On Fri, Dec 13, 2013 at 11:25, Sawada Masahiko Wrote I attached the patch which have modified based on Robert suggestion, and fixed typo. I have reviewed the modified patch and I have some comments.. 1. Patch

Re: [HACKERS] Logging WAL when updating hintbit

2013-12-18 Thread Sawada Masahiko
2013/12/14 0:14 Tom Lane t...@sss.pgh.pa.us: Heikki Linnakangas hlinnakan...@vmware.com writes: I'm not totally satisfied with the name of the GUC, wal_log_hintbits. Me either; at the very least, it's short an underscore: wal_log_hint_bits would be more readable. But how about just

Re: [HACKERS] Logging WAL when updating hintbit

2013-12-19 Thread Sawada Masahiko
it as Committed. Thanks! I attached the patch which changes name from 'wal_log_hintbits' to 'wal_log_hints'. It gained the approval of plural. Regards, --- Sawada Masahiko wal_log_hints.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] Logging WAL when updating hintbit

2013-12-19 Thread Sawada Masahiko
On Fri, Dec 20, 2013 at 3:38 AM, Sawada Masahiko sawada.m...@gmail.com wrote: On Thu, Dec 19, 2013 at 12:37 PM, Amit Kapila amit.kapil...@gmail.com wrote: On Wed, Dec 18, 2013 at 11:30 AM, Michael Paquier michael.paqu...@gmail.com wrote: On Wed, Dec 18, 2013 at 11:22 AM, Amit Kapila amit.kapil

[HACKERS] Comment typo in src/backend/command/cluster.c

2014-01-20 Thread Sawada Masahiko
Hi all, Attached patch fixes the typo which is in src/backend/command/cluster.c. Regards, --- Sawada Masahiko fix_typo-cluster.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Add force option to dropdb

2014-01-27 Thread Sawada Masahiko
://wiki.postgresql.org/wiki/Developer_FAQ#What.27s_the_formatting_style_used_in_PostgreSQL_source_code.3F Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Fix comment typo in /src/backend/command/cluster.c

2014-01-27 Thread Sawada Masahiko
Hi all, Attached patch fixes the typo which is in src/backend/command/cluster.c. Regards, --- Sawada Masahiko fix_typo-cluster.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Fix comment typo in /src/backend/command/cluster.c

2014-01-27 Thread Sawada Masahiko
On 01/27/2014 10:24 PM, Sawada Masahiko wrote: Hi all, Attached patch fixes the typo which is in src/backend/command/cluster. c. Are you sure that's a typo? iff is usually short hand for if and only if. Oops, I made mistake. Thanks! Regards, - Masahiko Sawada -- Regards

Re: [HACKERS] Add force option to dropdb

2014-01-29 Thread Sawada Masahiko
On Tuesday, January 28, 2014 4:17 AM, Sawada Masahiko sawada.m...@gmail.com wrote: On 2014年1月17日 0:56, salah jubeh s_ju...@yahoo.com wrote: If the user owns objects, that will prevent this from working also. I have the feeling that adding DROP OWNED BY and/or REASSIGNED OWNED BY calls to this utility

Re: [HACKERS] [PATCH] pg_basebackup: progress report max once per second

2014-01-31 Thread Sawada Masahiko
On Tue, Jan 21, 2014 at 7:17 AM, Oskari Saarenmaa o...@ohmu.fi wrote: 18.11.2013 07:53, Sawada Masahiko kirjoitti: On 13 Nov 2013, at 20:51, Mika Eloranta m...@ohmu.fi wrote: Prevent excessive progress reporting that can grow to gigabytes of output with large databases. I got error

Re: [HACKERS] [PATCH] pg_basebackup: progress report max once per second

2014-02-02 Thread Sawada Masahiko
On Sat, Feb 1, 2014 at 8:29 PM, Oskari Saarenmaa o...@ohmu.fi wrote: 31.01.2014 10:59, Sawada Masahiko kirjoitti: I think the idea in the new progress_report() call (with force == true) is to make sure that there is at least one progress_report call that actually writes the progress report

[HACKERS] 'dml' value for log_statement

2014-02-06 Thread Sawada Masahiko
DML. This patch allows the user to set in detail the setting. The server logs statement only when INSERT. UPDATE, DELETE and TRUNCATE statement are executed. ( same as 'mod' value which does not log the DDL) Comments? Regards, --- Sawada Masahiko log_statement_dml.patch Description

[HACKERS] pg_basebackup skips pg_replslot directory

2014-02-17 Thread Sawada Masahiko
not start. I got following FATAL error when the standby server starts. FATAL: could not open directory pg_replslot: No such file or directory Is this a bug? Attached file solves it by including pg_replslot directory as empty directory. Please give feedback. Regards, --- Sawada Masahiko

Re: [HACKERS] pg_basebackup skips pg_replslot directory

2014-02-17 Thread Sawada Masahiko
On Tue, Feb 18, 2014 at 2:07 AM, Andres Freund and...@2ndquadrant.com wrote: Hi, On 2014-02-18 02:01:58 +0900, Sawada Masahiko wrote: I found strange behavior of PostgreSQL of HEAD while using pg_basebackup. pg_basebackup skips pg_replslot directory since

[HACKERS] The behavior of CheckRequiredParameterValues()

2014-03-04 Thread Sawada Masahiko
. In this case, I think that the standby server didn't need to confirm wal_level value of ControlFile. I think that it should confirm value which is written in postgreql.conf. I might be missing something. Please let me know that. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing

Re: [HACKERS] The behavior of CheckRequiredParameterValues()

2014-03-05 Thread Sawada Masahiko
On Wed, Mar 5, 2014 at 5:13 PM, Amit Langote amitlangot...@gmail.com wrote: On Wed, Mar 5, 2014 at 12:07 PM, Amit Langote amitlangot...@gmail.com wrote: On Wed, Mar 5, 2014 at 2:09 AM, Sawada Masahiko sawada.m...@gmail.com wrote: xlog.c:6177 if (ControlFile-wal_level

[HACKERS] add line number as prompt option to psql

2014-06-12 Thread Sawada Masahiko
-id/cafj8prc1rupk6+cha1jpxph3us_zipabdovmceex4wpbp2k...@mail.gmail.com Please give me feedback. Regards, --- Sawada Masahiko psql-line-number_v1.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Set new system identifier using pg_resetxlog

2014-06-25 Thread Sawada Masahiko
log reset $ pg_controldata data | grep Database system identifier Database system identifier: 18446744073709551615 pg_resetxlog is finished successfully, but system identifier was not changed. Also I think that checking data about number of digits is needed. regards -- Sawada Masahiko

Re: [HACKERS] TODO : Allow parallel cores to be used by vacuumdb [ WIP ]

2014-06-25 Thread Sawada Masahiko
succeeded at 214 with fuzz 2 (offset 5 lines). Hunk #8 FAILED at 223. Hunk #9 succeeded at 374 with fuzz 1 (offset 35 lines). Hunk #10 FAILED at 360. Hunk #11 FAILED at 387. 3 out of 11 hunks FAILED -- saving rejects to file src/bin/scripts/vacuumdb.c.rej --- Sawada Masahiko On Friday, March 21

Re: [HACKERS] Set new system identifier using pg_resetxlog

2014-06-26 Thread Sawada Masahiko
:00010002 -- $ pg_resetxlog -s0 data Transaction log reset $ pg_controldata data | grep Database system identifier Database system identifier: 6029284919152642525 this patch dose not works fine with -s0. Regards, -- Sawada Masahiko On Thursday, June 26, 2014

Re: [HACKERS] TODO : Allow parallel cores to be used by vacuumdb [ WIP ]

2014-07-01 Thread Sawada Masahiko
=30' Try vacuumdb --help for more information. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] TODO : Allow parallel cores to be used by vacuumdb [ WIP ]

2014-07-02 Thread Sawada Masahiko
On Wed, Jul 2, 2014 at 2:27 PM, Dilip kumar dilip.ku...@huawei.com wrote: On 01 July 2014 22:17, Sawada Masahiko Wrote, I have executed latest patch. One question is that how to use --jobs option is correct? $ vacuumdb -d postgres --jobs=30 I got following error. vacuumdb: unrecognized

Re: [HACKERS] add line number as prompt option to psql

2014-07-06 Thread Sawada Masahiko
On Fri, Jun 20, 2014 at 7:17 PM, Jeevan Chalke jeevan.cha...@enterprisedb.com wrote: Hi Sawada Masahiko, I liked this feature. So I have reviewed it. Changes are straight forward and looks perfect. No issues found with make/make install/initdb/regression. However I would suggest removing

Re: [HACKERS] add line number as prompt option to psql

2014-07-09 Thread Sawada Masahiko
to remove them. I added them to latest patch. Regards, --- Sawada Masahiko psql-line-number_v3.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] add line number as prompt option to psql

2014-07-10 Thread Sawada Masahiko
of cur_line 0. Regards, --- Sawada Masahiko psql-line-number_v4.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] timeout of pg_receivexlog --status-interval

2014-07-10 Thread Sawada Masahiko
select() function with NULL of fourth argument. the attached patch allows to execute select() with NULL, i.g., pg_receivexlog.c will wait until can read socket without timeout, if -s is specified to 0. Regards, --- Sawada Masahiko receivexlog-timout.patch Description: Binary data -- Sent

Re: [HACKERS] add line number as prompt option to psql

2014-07-11 Thread Sawada Masahiko
, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] add line number as prompt option to psql

2014-07-11 Thread Sawada Masahiko
On Fri, Jul 11, 2014 at 11:01 PM, Alvaro Herrera alvhe...@2ndquadrant.com wrote: Jeevan Chalke wrote: On Fri, Jul 11, 2014 at 3:13 PM, Sawada Masahiko sawada.m...@gmail.com wrote: And the line number should be switched to 1 when line number has reached to INT_MAX? Yes, when it goes

Re: [HACKERS] timeout of pg_receivexlog --status-interval

2014-07-15 Thread Sawada Masahiko
On Tue, Jul 15, 2014 at 7:38 PM, Fujii Masao masao.fu...@gmail.com wrote: On Thu, Jul 10, 2014 at 11:10 PM, Sawada Masahiko sawada.m...@gmail.com wrote: Hi, At 1047 line of receivelog.c:CopyStreamPoll(), we set NULL to timeoutptr variable. if the value of timeoutprt is set NULL

Re: [HACKERS] add line number as prompt option to psql

2014-08-14 Thread Sawada Masahiko
On Sat, Jul 12, 2014 at 2:19 AM, Alvaro Herrera alvhe...@2ndquadrant.com wrote: Sawada Masahiko wrote: As you said, if line number reached UINT_MAX then I think that this case is too strange. I think INT_MAX is enough for line number. My point is not whether 2 billion is a better number

Re: [HACKERS] pg_receivexlog --status-interval add fsync feedback

2014-08-16 Thread Sawada Masahiko
patch modifies argument of some function (e.g., Handle CopyStream, Process LogDate Msg), and add the similar code to each function. I don't think it is good approach. For example, I think that we should gather these code into one function. Thought? Regards, --- Sawada Masahiko -- Sent via

Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: [HACKERS] HEAD seems to generate larger WAL regarding GIN index

2014-08-16 Thread Sawada Masahiko
the patch This time, attached. I think that this patch should be rebased. It contains garbage code. Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql

[HACKERS] After switching primary server while using replication slot.

2014-08-18 Thread Sawada Masahiko
think that we should make master server to notify about removal of WAL segment to all standby servers. And the standby servers recycle WAL segments files base on that information. Thought? -- Regards, --- Sawada Masahiko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

  1   2   3   >