is doing now, and whether this vacuum have any problem or not.
Maybe, For DBAs,
It might be better to show vacuum progress in pg_stat_activity.
(if we'd do, add a free-style column like "progress" ?)
This column might also be able to use for other long time commands
like ANALYZE, CREATE
t the overlap between my use of \connect
> and my use of debuggers is tiny.
Thank you all!
My hack is going to be much smoother.
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
E-Mail: nao-an...@xc.jp.nec.com
---
--
Sent via pgsql-hackers mailing list (
Hi, Andres, Marko
> Seems easier to set this in .psqlrc:
oops! I've never noticed..
Thank you for your comment.
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
E-Mail: nao-an...@xc.jp.nec.com
---
--
Sent via pgsql-hackers mailing list (pgsql
Process ID
pid
--
1716
(1 row)
---
How do you like it?
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
E-Mail: nao-an...@xc.jp.nec.com
---
psql_show_backend_pid.patch
Description: psql_show_backend_pid.patch
--
Sent via pgs
to hate pg_statsinfo,
I think this package is a very convinient tool)
Everyone will be able to do more easily tuning of VACUUM.
That's all I want.
Any comments are welcome!
Best Regards,
Naoya Anzai
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
E-Mail: nao-an...@xc.jp.
");
> >
> >
> > txid_current()
> > bigint
> > - get current transaction ID
> > + get current transaction ID, assigning a new one if current
> > transaction does not have one
>
_count
autovacuum_count
analyze_count
autoanalyze_count
If hackers agree with my point,
I'd like to make a patch for these features.
Any comments are welcome.
Best Regards,
Naoya Anzai
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
E-Mail: nao-an...@xc.jp.nec.com
this block.
Outside of the transaction-block, returns a next transaction-id(but it is
consumed by this function).
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
E-Mail: nao-an...@xc.jp.nec.com
---
--
Sent via pgsql-hackers mailing list (pgsql-hackers@
st a
read-only function.
I found a replaceable function by walking through pg-code, that is
GetStableLatestTransactionId(void).
I attached a patch which changing just 1-line.
Could you please check the code?
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
st a
read-only function.
I found a replaceable function by walking through pg-code, that is
GetStableLatestTransactionId(void).
I attached a patch which changing just 1-line.
Could you please check the code?
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
Hi, Michael
I thought about VACOPT_VERBOSE again.
As a result, I think you should not delete VACOPT_VERBOSE.
According to the last mail I have posted, the difference of
manual-vacuum log and auto-vacuum log exists clearly.
So, at least you should not touch the mechanism of VACOPT_VERBOSE
until
Hi, Michael
I found that definition of VERBOSE and log_autovacuum is not
pretty match. For example, "VERBOSE" can output logs of
scanning indices and scanning detail of analyze, but
log_autovacuum can't output them.
Please see following sequences.
1. execute these queries.
DROP TABLE t1;
C
>> You mean that ...
>> Log_autovacuum_min_duration assumes a role of VACOPT_VERBOSE.
>> Even if this parameter never use currently for manual vacuum,
>> log_autovacuum_min_duration should be set zero(anytime output)
>> when we executes "VACUUM(or ANALYZE) VERBOSE".
>> Is my understanding correct?
,
I think it's ideal that we will prepare a new parameter like
a log_min_duration_vacuum(and log_min_duration_analyze) which
integrating "VERBOSE feature" and "log_autovacuum_min_duration".
Regards,
---
Naoya Anzai
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Thanks for your reply.
>> Feature test
>>
(snip)
> I thought about using a
> special value like -2 to define the behavior you are mentioning here,
> aka with "-2" disable custom value and GUC parameter but I don't think
> it is worth adding as that's an ugly 3 line of code of
mistake.
All of them have passed.
---
Naoya Anzai
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
The following review has been posted through the commitfest application:
make installcheck-world: tested, failed
Implements feature: tested, failed
Spec compliant: tested, failed
Documentation:tested, failed
Hi,
I'm Naoya Anzai.
I've been working as a
rs.
It is really good if PostgreSQL gave us a message such as a replication abort
warning:
###
WARNING: canceling wait for synchronous replication due to user request
DETAIL: The transaction has already committed locally, but might not have been
replicated to the standby.
###
Regards,
Naoya
to reconfirm his action
> results with database before concluding anything.
I see.
Now, I understand that ProcessInterrupts Error (ProcDie, QueryCancel,
ClientLost..) does not mean "That query has been RollBacked".
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Soluti
alled in many many situations..
Could you please confirm it?
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Solution Inovetors, Ltd.
E-Mail: anzai-na...@mxu.nes.nec.co.jp
---
postgresql-fe7337f_elog.patch
Description: postgresql-fe7337f_elog.patch
--
Sent via pgsql-hackers m
;ready for committer".
I think so too.
In boot by Service, CurrentDirectory seems to be "C:/Windows/system32".
So, you have to set a relative data directory path that the starting point to
be "C:/Windows/system32".
>
> Thanks and Regards,
> Kumar Rajeev Rastogi
&
; > On Thu, Oct 31, 2013 at 1:44 AM, Asif Naeem wrote:
> >> On Thu, Oct 31, 2013 at 10:17 AM, Amit Kapila
> >> wrote:
> >>>
> >>> On Tue, Oct 29, 2013 at 12:46 PM, Naoya Anzai
> >>> wrote:
> >>> > Hi Sandeep
> >>>
ing space is vulnerable and can be exploited on Windows" to get the
> attention.. :)
>
> BTW, in your case, the file "Program" should be an exe and not just any other
> file to exploit this vulnerability. Right?
>
>
> On Tue, Oct 29, 2013 at 11:34 AM, Naoya
es-not-start-td5774206.html
Regards,
Naoya
> So, this is not an installer issue. Is this bug raised to the PostgreSQL
> community? If yes, you should submit the patch there.
>
>
> On Tue, Oct 29, 2013 at 6:23 AM, Naoya Anzai
> wrote:
>
>
> Hi, Asif
>
cessing enclosed in quotation should do in both conditions.
Regards,
Naoya
---
Naoya Anzai
Engineering Department
NEC Soft, Ltd.
E-Mail: anzai-na...@mxu.nes.nec.co.jp
---
> Hi Sandeep,
>
> PFA Naoya's patch (pg_ctl.c.patch).
>
> Hi Naoya,
ile start
> server starting
>
>
> Can you please share the exact steps ?. Thanks.
>
>
> Regards,
> Muhammad Asif Naeem
>
>
>
> On Mon, Oct 28, 2013 at 10:26 AM, Naoya Anzai
> wrote:
>
>
> Hi All,
>
> I have found a case t
ries to create a process using the other file such
as "Program", so the service fails to start.
Accordingly, I think that the command path should be
enclosed in quotation.
I created a patch to fix this failure,
So could anyone confirm?
Regards,
Naoya
---
Naoya Anzai
Engineering Dep
27 matches
Mail list logo
