From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | four minor proposals for 9.5 |
Date: | 2014-03-19 15:34:08 |
Message-ID: | CAFj8pRDyu5aa8QVSu9vDUJpdvrH+U4De0ZTtMELGGKKVwvcnRA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
2. fatal verbose - this patch ensure a verbose log for fatal errors. It
simplify a investigation about reasons of error.
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.
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.
Do you thinking so these patches can be generally useful?
Regards
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-03-19 16:28:28 | Re: jsonb status |
Previous Message | Tom Lane | 2014-03-19 14:55:51 | Re: Re: Leaking regexp_replace in 9.3.1 ? (was: [HACKERSUninterruptable regexp_replace in 9.3.1 ?) |