From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | bwest1(at)cox(dot)net |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: ALTER SERVER SYNTAX ISSUE |
Date: | 2018-10-31 11:57:18 |
Message-ID: | 19424.1540987038@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
=?utf-8?q?PG_Doc_comments_form?= <noreply(at)postgresql(dot)org> writes:
> I found that the alter server statement below does not work:
> ALTER SERVER foo OPTIONS (host 'foo', dbname 'foodb');
> but this does:
> ALTER SERVER foo OPTIONS (set host 'foo', set dbname 'foodb');
Hm, define "does not work". Those aren't equivalent: the first
form adds options that weren't already set, while the second one
changes the values of already-set options. (The SQL committee
were being unreasonably nitpicky in not providing an add-or-replace
choice, IMO, but that's how the spec is written.)
Is your complaint just that this is inadequately documented?
I see that it's not spelled out in so many words on that page.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2018-11-01 00:26:53 | Tipos de datos enteros |
Previous Message | Tatsuo Ishii | 2018-10-31 00:33:03 | Re: question, converting version 11 sgml files at once. |