Re: four minor proposals for 9.5 - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: four minor proposals for 9.5
Date
Msg-id CAFj8pRAfPgLLFCdcC5bVZ_vqC2S_Du=+VJFcwmO7xJWU1Wj62g@mail.gmail.com
Whole thread Raw
In response to four minor proposals for 9.5  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: four minor proposals for 9.5  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Hello

After week, I can to evaluate a community reflection:


2014-03-19 16:34 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:
Hello

I wrote a few patches, that we use in our production. These patches are small, but I hope, so its can be interesting for upstream:

1. cancel time - we log a execution time cancelled statements

there is a interest
 

2. fatal verbose - this patch ensure a verbose log for fatal errors. It simplify a investigation about reasons of error.

not too much
 

3. relation limit - possibility to set session limit for maximum size of relations. Any relation cannot be extended over this limit in session, when this value is higher than zero. Motivation - we use lot of queries like CREATE TABLE AS SELECT .. , and some very big results decreased a disk free space too much. It was high risk in our multi user environment. Motivation is similar like temp_files_limit.

is not a interest
 

4. track statement lock - we are able to track a locking time for query and print this data in slow query log and auto_explain log. It help to us with lather slow query log analysis.

there is a interest

So I'll prepare a some prototypes in next month for

1. log a execution time for cancelled queries,
2. track a query lock time

Regards

Pavel
 

Do you thinking so  these patches can be generally useful?

Regards

Pavel

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: four minor proposals for 9.5
Next
From: Christoph Berg
Date:
Subject: Re: [patch] Adding EXTRA_REGRESS_OPTS to all pg_regress invocations