Hi Stephen,
As you said, I'm not good at English, so I'm glad you handle this thread.
I'll wait for the good changing.
Thank you very very much!
regards,
--
Tomonari Katsumata
2014-09-23 14:23 GMT+09:00 Stephen Frost :
> * Tom Lane (t...@sss.pgh.pa.us)
Hi,
I've update my entry.
[rounding up time value less than its unit]
https://commitfest.postgresql.org/action/patch_view?id=1507
regards,
-
Tomonari Katsumata
(2014/09/12 7:03), Tomas Vondra wrote:
> On 11.9.2014 21:14, Petr Jelinek wrote:
>> On 11/09/14 18:59
t to change current behavior except non-zero value yields
a zero. A zero rounded down from non-zero gets an error.
I attached new patch.
This includes a document about above behavior as Heikki suggested.
regards,
--
Tomonari Katsumata
2014-08-27 6:49 GMT+09:00 David G Johnston :
70s->1
Although my original complaint is fixed, I'm worried about this change will
make users confusing.
Is it better to raise a message(ex. INFO) when a value less than required
unit is set?
2014-08-21 21:00 GMT+09:00 Heikki Linnakangas :
> On 07/10/2014 09:52 AM, Tomonari Katsum
Hi Robert,
Thank you for checking this!
I've added it to commitfest.
https://commitfest.postgresql.org/action/patch_view?id=1507
regards,
Tomonari Katsumata
2014-07-12 6:07 GMT+09:00 Robert Haas :
> On Thu, Jul 10, 2014 at 2:52 AM, Tomonari Katsumata
> wrote:
cause some GUCs have special meaning for 0.
And then I made a patch for this.
Please check the attached patch.
regards,
---
Tomonari Katsumata
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 04ddd73..9aaffb0 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src
mps to a page of pg_receivexlog.
It should jump to pg_recvlogical(app-pgrecvlogical.html).
regards,
----
Tomonari Katsumata
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
I think "A backup started with pg_stop_backup()" should be
"A backup started with pg_start_backup()".
This is a bug about source comment, so it's not big problem.
But I want to fix the comment.
See attached patch.
regards,
--
Tomonari Katsumata
diff --git a/src/
Hi
2014-03-10 23:45 GMT+09:00 Tom Lane :
> Tomonari Katsumata writes:
> > Adding FATAL and PANIC to client_min_messages is done at below-commit.
> > 8ac386226d76b29a9f54c26b157e04e9b8368606
> >
> http://git.postgresql.org/gitweb/?p=p
Hi Tom, Bruce,
Thank you for your response.
(2014/03/09 2:12), Tom Lane wrote:
> Bruce Momjian writes:
>> On Sat, Mar 8, 2014 at 11:31:22AM -0500, Tom Lane wrote:
>>> Tomonari Katsumata writes:
>>>> [ client_min_messages = info is not documented ]
>
>>&
ice
# warning
# error
also I couldn't understand the reason of disappearing
'info', 'fatal' and 'panic' from them.
My proposal is all valid values should be present for us
Hi Heikki,
I need PostgreSQL9.3 which fixed this problem.
It didn't happen in PostgreSQL9.2, so I agree
with your proposal which changes are done
against 93_STABLE and master.
Can you fix this in next release(9.3.3)?
Tomonari Katsumata
(2014/01/13 20:16), Heikki Linnak
Hi,
Somebody is reading this thread?
This problem seems still remaining on REL9_3_STABLE.
Many users would face this problem, so we should
resolve this in next release.
I think his patch is reasonable to fix this problem.
Please check this again.
regards,
--
Tomonari
e had sufficent
> textual differences from the BSD License to be a different license.
>
> I've requested that the spurious "file name" reference be removed.
>
Thank you for checking it soon.
I understands that "the PostgreSQL license" does not require
any spec
ile are all required by the
license.
So I have confused why PostgreSQL has a "COPYRIGHT" file instead of
"LICENSE".
Anybody knows the reason?
And is this non problem thing?
regards,
-
Tomonari Katsumata
from somewhere (the release notes?), but I
> don't see any need to change anything in the release.
>
Yes, I was not thinking about changing current 9.3 behavior.
So I think it's enough to know the impact and how to avoid that
on the release notes.
thanks a lot!
regards,
-
10
11
(11 rows)
regards,
----
NTT Software Corporation
Tomonari Katsumata
(2013/08/13 19:16), Szymon Guz wrote:
> On 13 August 2013 11:43, Tomonari Katsumata <
> katsumata.tomon...@po.ntts.co.jp> wrote:
>
>> Hi,
>>
>> Could anyone tell me how to cre
n the restored database.
I want to make these views read-only like PostgreSQL9.2.
How can I do this? Should I make access control on users ?
(Sorry, I couldn't find any explanations on document.)
regards,
NTT Software Corporation
Tomonari Katsumata
--
Sent via pgsql-hacke
_target_xxx)
occur at the same time.
--
1) is created, but promoting completes by another trigger.
Both cases 1) remains on the server.
If user doesn't know it and make a standby on the server,
the standby will promote soon.
I think this is not so big problem, but not user-friendly.
Agains
e would be smaller than change to pg_ctl.
And this would allow us to treat ${PGDATA}/promote and trigger_file only.
(because ${PGDATA}/fast_promote is not created automatically)
regards,
---
Tomonari Katsumata
h are
created by user as a trigger_file or "pg_ctl promote" command.
---
Tomonari Katsumata
2013/7/30 Fujii Masao
> On Sat, Jul 27, 2013 at 6:57 PM, Tomonari Katsumata
> wrote:
> > Hi,
> >
> >
> >>>> Yes, it prevents PROMOTE_SIGNAL_FILE
;>
>> If it is seldom to happen its crash soon after promoting
>> and "fast promte" never breaks consistency of database cluster,
>> I think we don't need normal promotion.
>
> You can execute checkpoint after fast promotion for that.
>
OK.
Then I think we should do below things.
- removing normal promotion at all from source
- adding the know-how you suggest on document
Are there any objection?
regards,
---
Tomonari Katsumata
Hi Fujii-san,
Thank you for response.
(2013/07/25 21:15), Fujii Masao wrote:
> On Thu, Jul 25, 2013 at 5:33 PM, Tomonari Katsumata
> wrote:
>> Hi,
>>
>> Now I'm seeing xlog.c in 93_stable for studying "fast promote",
>> and I have a question.
>
OTE_SIGNAL_FILE);
9937 unlink(PROMOTE_SIGNAL_FILE);
9938 fast_promote = true;
9939 }
---
Is this command necesary ?
regards,
------
NTT Software Corporation
Tomonari Katsumata
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscripti
Hi, Michael
2013/1/23 Michael Paquier
>
>
> On Wed, Jan 23, 2013 at 5:46 PM, Tomonari Katsumata <
> t.katsumata1...@gmail.com> wrote:
>
>> ex:
>>
>> primary_conninfo = 'port=5432 standby_mode=master-cascade'
>> primary_conninfo =
Hi, Tom
Thank you for comments.
> Tomonari Katsumata writes:
> >> Why is it better to do this with a privilege, rather than just using
> >> pg_hba.conf?
>
>
> > You are right.
> > Handling with pg_hba.conf is an easy way.
>
> > But I thin
u scanned it to be sure that the same node
>has not been scanned, what would mean that you are in a cycle.
>
I think this is very complicated.
At least, now I can't solve it...
If someday we can detect it, this kind of switch will be needed.
Because some users may need the cyclic situation.
I'm not insisting to use replication-role, but
I want something to control this behavior.
regards,
NTT Software Corporation
Tomonari Katsumata
this yet,
but I want any comments whether this change is needed or not.
regards,
-
NTT Software Corporation
Tomonari Katsumata
*** a/src/backend/commands/user.c
--- b/src/backend/commands/user.c
***
*** 250,256 CreateRole(CreateRoleStmt *stmt)
if (dcanlogin)
28 matches
Mail list logo