From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Victor Yegorov <vyegorov(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ALTER TYPE ... ADD VALUE issue |
Date: | 2014-10-20 19:26:33 |
Message-ID: | 544561E9.8070707@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/20/2014 12:03 PM, Tom Lane wrote:
> Victor Yegorov <vyegorov(at)gmail(dot)com> writes:
>> 2014-10-20 21:43 GMT+03:00 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:
>>> With \set AUTOCOMMIT off the COMMIT ended one transaction block and
>>> started another.
>
>> I don't think `COMMIT` starts a new transaction block here,
>> as I can run `VACUUM` after it, and vacuum also cannot be run inside
>> transaction block.
>
> psql knows not to issue BEGIN before a VACUUM command. It doesn't
> know that about ALTER TYPE ... ADD VALUE.
Forget about the \set confusion, just realized I was ending the \set
with an ; which was causing the message.
>
> regards, tom lane
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | David G Johnston | 2014-10-20 20:28:12 | Re: ALTER TYPE ... ADD VALUE issue |
Previous Message | Adrian Klaver | 2014-10-20 19:18:13 | Re: ALTER TYPE ... ADD VALUE issue |