| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
| Cc: | Christoph Berg <cb(at)df7cb(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER SYSTEM RESET? |
| Date: | 2014-06-27 04:22:57 |
| Message-ID: | CAA4eK1LvqBfNdoGO4YUZMOgcHg7Mi_9oVD2B5XJPtU_KTXLdew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 26, 2014 at 8:17 PM, Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> wrote:
> On 06/26/2014 05:07 AM, Amit Kapila wrote:
> > I think it will make sense if we support RESET ALL as well similar
> > to Alter Database .. RESET ALL syntax. Do you see any reason
> > why we shouldn't support RESET ALL syntax for Alter System?
>
> Yes, that makes sense. I've added that in the attached version 2 of the
> patch.
I think the idea used in patch to implement RESET ALL is sane. In passing
by, I noticed that modified lines in .sgml have crossed 80 char
boundary which
is generally preferred to be maintained..
Refer below modification.
! values to the <filename>postgresql.auto.conf</filename> file. Setting
the parameter to
! <literal>DEFAULT</literal>, or using the <command>RESET</command>
variant, removes the configuration entry from
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Johnson | 2014-06-27 04:47:47 | Index-only scans and non-MVCC snapshots |
| Previous Message | Amit Kapila | 2014-06-27 03:41:10 | Re: postgresql.auto.conf and reload |